error when used in an engine
See original GitHub issueIt works when in a normal in-repo-addon’s dependencies, but when I convert it to an engine, I get:
The Broccoli Plugin: [BroccoliMergeTrees] failed with:
Error: ENOENT: no such file or directory, open '/Users/kelly.selden/Sites/dustbunny/tmp/source_map_concat-input_base_path-Zc6lPjy5.tmp/vendor/ember-test-selectors/patch-component.js'
at Object.fs.openSync (fs.js:584:18)
at Object.fs.readFileSync (fs.js:491:33)
at SourceMap.addFile (/Users/kelly.selden/Sites/dustbunny/node_modules/fast-sourcemap-concat/lib/source-map.js:75:31)
at /Users/kelly.selden/Sites/dustbunny/node_modules/broccoli-concat/concat.js:200:16
at Array.forEach (native)
at Concat.<anonymous> (/Users/kelly.selden/Sites/dustbunny/node_modules/broccoli-concat/concat.js:198:24)
at /Users/kelly.selden/Sites/dustbunny/node_modules/fast-sourcemap-concat/lib/source-map.js:399:12
at initializePromise (/Users/kelly.selden/Sites/dustbunny/node_modules/rsvp/dist/rsvp.js:567:5)
at new Promise (/Users/kelly.selden/Sites/dustbunny/node_modules/rsvp/dist/rsvp.js:1039:33)
at SourceMap.end (/Users/kelly.selden/Sites/dustbunny/node_modules/fast-sourcemap-concat/lib/source-map.js:386:10)
The broccoli plugin was instantiated at:
at BroccoliMergeTrees.Plugin (/Users/kelly.selden/Sites/dustbunny/node_modules/broccoli-plugin/index.js:7:31)
at new BroccoliMergeTrees (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:16:10)
at Function.BroccoliMergeTrees [as _upstreamMergeTrees] (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:10:53)
at mergeTrees (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/lib/broccoli/merge-trees.js:85:33)
at Class.treeForPublic (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-engines/lib/engine-addon.js:759:16)
at Class._treeFor (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/lib/models/addon.js:551:33)
at Class.treeFor (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-engines/lib/engine-addon.js:933:23)
at project.addons.map.addon (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/lib/broccoli/ember-app.js:557:22)
at Array.map (native)
at EmberApp.addonTreesFor (/Users/kelly.selden/Sites/dustbunny/node_modules/ember-cli/lib/broccoli/ember-app.js:555:32)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Ways to detect an error in your car engine automatically
Professional mechanics use car computerized diagnostics to detect errors with the car engine that are causing it to perform poorly.
Read more >Engine Error Messages - Conitec
Aside from script syntax errors, error or warning messages indicating a malfunction can be issued by the engine at startup or during runtime....
Read more >Common Vehicle Error Codes - Bob Moore Auto Group
Most Common Error Codes · Fuel Evaporative System Leaks · Wheel Speed Variation · Low Voltage Codes · Engine Misfire Codes · Transmission...
Read more >System Error Warnings Explained - Ron Lewis Ford
The often misunderstood check engine light or "service engine soon" message can mean many different things. It could be a misfiring engine, a...
Read more >4 Signs Your Engine Has a Serious Problem - YouTube
Chapters. View all · Engine Misfire · Engine Misfire · Engine Misfire · Running Too Lean · Running Too Lean · Running Too...
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
Ah you’re talking about your internals. I changed to host, and it is working now.
I have this problem when using
ember-test-selectors
within a lazy-loaded engine. Seems to related to this issue here. When running host app’s test I got error related toember-test-selectors/patch-component.js
not available. Changing back to using app.import will solve the problem but I’m not sure how to fix for all use cases.