-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build error: "don't know how to insertURL /assets/undefined" #798
Comments
confirm: I got this error yesterday in an addon and made it go away by manually adding webpack @v5 to my package.json |
I could refer to the master branch of test-setup as an interim solution, but wonder if there is anything left blocking that release? (other than your personal time of course) Anything I/we can do? |
Ran into the same thing with |
I'm experiencing this issue as well. I tried |
The main thing blocking release is that changes in (I think) ember-cli-babel have left a large swath of embroider's test suite falling. |
Seeing the same issue with ember-page-title. Tried with auto-import v2 and get the same result as well. But an older version of auto-import might have been used since some deps don't use v2. When using resolutions and setting auto-import to v2, I get this:
Looks like #792 will fix this. Any ideas when this will be released? |
0.41.0 fixes it for me with auto-import v1 in ember-page-title |
Confirm. Fixed in 0.41.0! |
Anyone know why tests would be hanging for embroider with errors like this?
They run for hours and never time out, so I cancel them, and then I see these types of errors. See this PR RobbieTheWagner/ember-shepherd#779 |
@rwwagner90 sounds like you need to use skipBabel setting for velocity maybe? #677 (comment) |
@knownasilya I tried that in RobbieTheWagner/ember-shepherd#779 and it still seems to hang with the same error. @ef4 any ideas here? |
After re-enabling embroider test scenarios in
ember-bootstrap
, I am getting this error in CI, also when adding the embroider dependencies locally to this PR (which could serve as a reproduction).It has worked before, so this seems like a regression.
I debugged this a bit in node:
the error is thrown in
@embroider/webpack
herein the previous step of the call stack, the
match
forassets/dummy.js
seems pretty broken:Same when looking at
stats.entrypoints
map forassets/dummy.js
(same forassets/tests.js
):Haven't investigated any further. Any idea?
The text was updated successfully, but these errors were encountered: