Support for lazy engines about ember-auto-import HOT 3 OPEN

Yes. I'm pretty sure non-lazy engines are already supported.

For lazy-engines, I think they technically already work (meaning nothing actually breaks), but everything imported from the lazy engine would end up in vendor.js, so would not be lazy.

Fixing this is probably not very hard. Right now, we pick one package (meaning an app or addon) that is using ember-auto-import to be the primary and actually do the bundling. All the others that are using ember-auto-import just hook their source trees into the primary's import analyzer.

Instead of picking a single global primary, each package should look upward through its ancestor packages and stop when it finds a lazy engine, and only share the bundler within the engine.

from ember-auto-import.

While I would still like to fix this issue directly, a workaround is now available. Lazy engines can use dynamic import() to lazily load their own dependencies.

from ember-auto-import.

Hello! we're doing some issue triage and wanted to provide resolution to various issues, and provide closure for some issue, or confirm that they are still a problem, and that we haven't forgotten.

For lazy engines, they are supported under embroider, here is an example test, using a lazy engine

In ember-auto-import, the issue could still be present (as it is now 5 years later), and it would be fantastic to have a PR for a failing test scenario (maybe even copying from the embroider test!).

Thank you!!

from ember-auto-import.