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

How will this change with Ivy? #6

Open
fr0 opened this issue Jun 27, 2019 · 4 comments
Open

How will this change with Ivy? #6

fr0 opened this issue Jun 27, 2019 · 4 comments

Comments

@fr0
Copy link

fr0 commented Jun 27, 2019

Firstly, thanks for creating and sharing this. I'm going to try using it, as I've been unsuccessful with all other approaches, usually due to lack of AoT support.

Do you have any thoughts or insights on how much the solution will have to change with Angular 9 once Ivy is the default?

Thanks again!

@waltiam
Copy link

waltiam commented Jan 23, 2020

We've tried this with Ivy enabled in 8.2 and it has not gone well. Debugging has dropped us deep in the core of SystemJS.

Are there any thoughts on moving past this road block?

@john-gouda
Copy link

Please refer to the following issue: #24

Ivy would be much easier to perform plugin architecture. Since Ivy introduced locality, which mean component factory logic is embedded as static property of component class. Means consumer of a given component doesn't need to know how to instantiate the component, and you don't have to rebuild the consumer if dependency's constructor signature got change.

@namnhcntt
Copy link

@jfgouda Could you have an example simple implement plugin archiatecture with ivy?

@john-gouda
Copy link

I got some time to fork and migrate both workspace and builder to Angular 9.
https://github.com/jfgouda/angular-plugin-architecture
Thx

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

No branches or pull requests

4 participants