You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a transitive dependency of a lazy-engine uses app.import() to load a package, it will end up in app's vendor.js instead of engine-vendor.js.
For example assume ember-d3 uses app.import to load d3.js, if my-lazy-engine depends on ember-d3, everything is fine and d3.js ends up in engine-vendor.js. But if my-lazy-engine depends on another-addon which depends on ember-d3, d3.js ends up in app's vendor and is not lazy-loaded anymore.
This might be because the the _findHost used in the case of transitive dep is not overwritten by ember-engines like the way direct dependency is.
The text was updated successfully, but these errors were encountered:
If a transitive dependency of a lazy-engine uses
app.import()
to load a package, it will end up in app'svendor.js
instead ofengine-vendor.js
.For example assume
ember-d3
usesapp.import
to loadd3.js
, ifmy-lazy-engine
depends onember-d3
, everything is fine andd3.js
ends up inengine-vendor.js
. But ifmy-lazy-engine
depends onanother-addon
which depends onember-d3
,d3.js
ends up in app's vendor and is not lazy-loaded anymore.This might be because the the
_findHost
used in the case of transitive dep is not overwritten by ember-engines like the way direct dependency is.The text was updated successfully, but these errors were encountered: