Will Code Splitting per "Ember Addon" be possible next?

[rwjblue]

I’m not 100% sure I understand the questions, but let me give it a shot…

@Daniel_Park

we want to “lazy load” each domain(ember addon) when user click the menu

Here you are asking if it will be possible to make a “lazy non-engine addon”? If so, then I think the answer is essentially that this should become possible with the “packager” work that is currently underway (unsure at the moment just how “simple” it will be, still a few unknown unknowns here)…

@Daniel_Park

we also want to build and deploy each domain separately (Building app as whole takes tens of minutes)

We are working (generally speaking) on many different ways to pre-build an addon so that the build times of host applications do not suffer.

---

Please check out the section on treeshaking and code splitting in:

Ember CLI, 2018 Edition

The Ember CLI team spent the day after EmberConf talking about our priorities for the upcoming year. We meet annually, and this time around we decided to publish the notes from our meeting to make sure our direction is transparent for everyone in the community. We asked the Ember community beforehand for feedback on the issues and pain points with Ember CLI. We do want to thank everyone who participated. Your feedback is very valuable! Here’s a summarized list of the most anticipated features,…