-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Ivy compiler #11
Comments
Any news? |
Maybe now, any news? |
@kondi0 @hadrien-toma Unfortunately, I was forced to abandon this solution and I do not have time to do any research or maintenance on this matter. |
I understand, it is kind to have tried and to share this status. Do you recommend to not use Ivy if using Angular Element then? I fear to do this choice because I suppose in the near future Ivy will be the only compiler available... Do you know if am I wrong? |
Your fear is absolutely justified - "View Engine is no longer available in Angular as of v13". So there is only Ivy compiler now, probably. I can't say that is no way to workaround about this and probably there is still a lot of potential in micro frontends in general. I can only say that in all of my projects in the past 2-3 years if I needed to extract some common things for multiple projects I went into "ng-packagr"-based solution and there were no problems with the Ivy. Unpredictability of the Angular Elements-based complex solutions was too huge to me to take risk in real-life projects. |
Alright, this is very useful feedback, thank you very much. |
Unfortunately "ng-packagr" helps with other kind of problems than this one and I am unable to help more. In case of Angular, Elements should be the right choice for creating such components for PHP-based apps. Maybe situation is not that bad and it's possible with AOT and/or Ivy now |
Noted, thank you very much for your help and time. |
No problem 😀 and thanks for appreciating. I hope I will find some time to investigate the case in higher Angular versions in the future. |
Wait for official support
angular/angular#30262 (comment)
The text was updated successfully, but these errors were encountered: