How will this change with Ivy?

[fr0]

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]

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]

Please refer to the following issue: https://github.com/alexzuza/angular-plugin-architecture/issues/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]

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

[john-gouda]

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