Skip to content
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

Open
bmagrys opened this issue Jun 16, 2019 · 9 comments
Open

Enable Ivy compiler #11

bmagrys opened this issue Jun 16, 2019 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@bmagrys
Copy link
Owner

bmagrys commented Jun 16, 2019

Wait for official support
angular/angular#30262 (comment)

@bmagrys bmagrys added the enhancement New feature or request label Jun 16, 2019
@bmagrys bmagrys self-assigned this Jun 16, 2019
bmagrys pushed a commit that referenced this issue Jun 16, 2019
bmagrys added a commit that referenced this issue Jun 16, 2019
@bmagrys bmagrys closed this as completed Jun 16, 2019
@bmagrys bmagrys reopened this Jun 16, 2019
@kondi0
Copy link

kondi0 commented Mar 5, 2020

Any news?

@hadrien-toma
Copy link

Maybe now, any news?

@bmagrys
Copy link
Owner Author

bmagrys commented Apr 19, 2022

@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.

@hadrien-toma
Copy link

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?

@bmagrys
Copy link
Owner Author

bmagrys commented Apr 19, 2022

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.

@hadrien-toma
Copy link

hadrien-toma commented Apr 19, 2022

Alright, this is very useful feedback, thank you very much.
May you point me to some information/documentation related to the solution you suggested around ng-packagr? My use case is to be able to use components developed with Angular in a PHP based website (so I need to package the web component in some way but I am only aware of Angular Element for this need).

@bmagrys
Copy link
Owner Author

bmagrys commented Apr 19, 2022

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 , but I can't quickly check this because this project uses ngx-build-plus in all configuration files, which is helpful for Angular Elements, but only up to version 9 of Angular.

@hadrien-toma
Copy link

Noted, thank you very much for your help and time.
By the way, I really find this repo is a masterpiece so thank you also for sharing it 👍.

@bmagrys
Copy link
Owner Author

bmagrys commented Apr 19, 2022

No problem 😀 and thanks for appreciating. I hope I will find some time to investigate the case in higher Angular versions in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants