Assertion Failed: Asset manifest does not list any available bundles.
See original GitHub issueI’ve created a standalone routable engine with ember-engines 0.4.0, ember-cli 2.10.0 and get this error if I call the engines index route (/things/
).
Assertion Failed: Asset manifest does not list any available bundles.
Consumer App router.js
:
this.mount('things', { as: 'things' });
Engine App routes.js
:
this.route('index', { path: '/' });
The engine is ‘installed’ via a symlink in the node_modules/
dir of the consuming ember-cli app. (See here why).
Any idea?
Issue Analytics
- State:
- Created 7 years ago
- Comments:33 (10 by maintainers)
Top Results From Across the Web
How to setup ember engines? - Stack Overflow
I get this error if I call the engines index route ( /thingy/ ):. Assertion Failed: Asset manifest does not list any available...
Read more >How to download AssetBundleManifest from Server with ...
The assetbundle manifest is an important one, as it allows you to query all available bundles and gather dependencies.
Read more >Error - [package-solution] No manifests were found
I am building an application customizer for our SharePoint online site, but i keep getting this error:- Error - [package-solution] No ...
Read more >On demand resources | Apple Developer Forums
They are receiving the following error: Caught exception downloading ODR asset ... Failed to find asset manifest for {bundleID = <bundle-id>; error: Error...
Read more >Building AssetBundles - Unity - Manual
By default, the AssetBundle option for assets is set to None, meaning the asset is not written into an AssetBundle but is instead...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like you’ve not added your engine as a dependency of your application in your applications
package.json
.Try adding
"thingy-frontend": "*"
to your applications devDependencies.@mike183 Thank you very much for you guidance! You helped us a lot 😃