@alan-agius4, Dynamic view composition is a base feature for our application framework (built on top of angular) and we are in trouble for the reasons you explained here. Can you give me a look on what you called "Dynamic view composition project"?

@gmaggiodev, dynamic view composition is still at design phase.

@alan-agius4 Could you please give us an estimation for when this will be done ? And Is there any workaround at the moment for Angular 9/10 for AOT + JIT or is there a proper way to implement such a thing ? Or as is there an estimation for the 'Dynamic view composition project' ? I am facing mostly the same problems as @gmaggiodev said.

@pcatuna you may have a look at this Uncaught (in promise): Error: Angular JIT compilation failed: '@angular/compiler' not loaded! in angular 9

I think exclude of TerserPlugin may help to decrease the generated size after side_effects set to false.

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

I'm more curious about your reference to ng-elephant. What is that?

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

This is something that should be addressed by the full team and not discarded because it doesn't have enough votes. This is not a trivial feature that users are asking for, this basically makes Ionic Angular-based apps unable to be built if we use dynamic components for alerts, for instance ( see https://github.com/jgerstle/ionic-custom-alert ).

What workaround is the Angular team proposing other than just leaving us with our hands tied "until it's done" ? Quite a bad design decision made with no workaround provided, other than disabling all optimizations. I just spent all day trying to work around this and it's been impossible, so I've had to revert back my app to Angular 11 and use enableIvy=false.

In case you want more use-cases, we also need it for our mobile app at Moodle: https://github.com/moodlehq/moodleapp

We need to render dynamic templates because Moodle sites can be extended with plugins, and templates will come from the server.