Can't resolve 'ember-cli-surge/blueprints/surge'
See original GitHub issueAfter having linked the latest embroider packages and trying to build/run the app, I get the following error:
Module not found: Error: Can’t resolve ‘ember-cli-surge/blueprints/surge’ in ‘/private/var/folders/qb/zkbx5mt13qggl5zc8h19fy4h0000gn/T/embroider/48c6b9/blueprints’
This is thrown from this line:
export { default } from ‘ember-cli-surge/blueprints/surge’;
I’m not sure if this is the correct way to import the blueprint, since it’s actually under
ember-cli-surge/blueprints/ember-cli-surge/index.js
(see here), but the build is successful if built the “classic” way (without Embroider).
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Can't resolve 'fs' when bundle with webpack #447 - GitHub
to webpack config file and the error is gone. Not sure how it works, It seems like webpack did some thing with fs...
Read more >Module not found: Error: Can't resolve 'fs' in dotenv/lib
To solve this: Create the .env file at the root level of you app; Name your variables beginning with REACT_APP_ // that's the...
Read more >How to fix 'Module not found: Can't resolve 'http' in ... - YouTube
Basically, just change 'react-scripts' to 4.0.2 in your package.json and run `npm install` again :D Follow me on Twitter: ...
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
It’s true that we don’t support blueprints in v2 addons yet. But that shouldn’t be relevant, because
ember generate
andember build
are completely disconnected from each other. Embroider only affects the build. Blueprints run un-affected by Embroider.This is a bug in ember-cli-surge. It is importing its blueprint code (which should only ever run in Node) into the app’s runtime (browser) code. Specifically, this file probably needs to get deleted.
Here is a workaround until upstream can be fixed:
To me this would imply that blueprints would just work without any extra action when switching to use Embroider. Do you interpret it differently?