No manifest generated for engine when external addon extends from ember-asset-loader about ember-asset-loader HOT 4 OPEN

Adding a dependency on ember-asset-loader does not inherently cause an asset manifest to be created. You need to either include ember-engines (which does create an assert manifest), or configure something in your application to use ManifestGenerator.extend itself.

from ember-asset-loader.

I can't actually tell what you are trying to do here. Are you trying to emit two asset manifests?

from ember-asset-loader.

There definitely is a bug here: lib/manifest-generator.js uses the second argument to contentFor to determine the modulePrefix which will not match the expected module prefix when app/config/asset-manifest.js module is evaluated.

Should be gathering the modulePrefix from the findHost result, not the second argument. That would resolve this specific error.

from ember-asset-loader.

Rob and I spoke offline. I have an external addon which lazily-loads a static asset on behalf of consuming host apps. We were using ember-asset-loader's loadAsset method to achieve this. The issue brought up in this ticket exists if the host app also depends on ember-engines, which itself depends on, and extends from, ember-asset-loader and therefore produces its own manifest.

In short, a host app with an engine which also brings in an external addon with ember-asset-loader will result in a fatal error.

We have decided that, for the time being, we will do our own simple script loading in our addon and remove ember-asset-loader as a dependency. Potentially in the near future we can modify ember-asset-loader to allow for loading of an asset without a manifest.

from ember-asset-loader.