Closed timiyay closed 3 years ago
Gah, I got stuck on this for a while, as soon as I open an issue I make progress 😬
This issue was caused by me copypasta'ing config from https://github.com/embroider-build/embroider#configuring-asset-urls:
packagerOptions: {
publicAssetURL: 'https://your-cdn-here.com/', // This should be a URL ending in "/"
}
publicAssetURL
should not be used for development
and test
builds, which is default behaviour in legacy builds. Once I made it conditional on production
builds, my tests started running.
The tests don't complete, they hang after the last test, and require Ctrl+C
to be pressed to exit and receive results.
I'm glad you were able to fix your problem and thanks for sharing the solution for future searchers who may hit the same issue.
But also, please file an issue for:
We're using 0.39, to avoid the issue where @embroider/webpack wants webpack 5, but other embroider packages or dependencies want webpack 4.
Because that is definitely not supposed to be a thing and I don't see any way to reproduce it.
Follow-up issue opened at https://github.com/embroider-build/embroider/issues/783
We're experimenting with
embroider
adoption on a new Ember 3.24 app.We're using 0.39, to avoid the issue where
@embroider/webpack
wants webpack 5, but other embroider packages or dependencies want webpack 4.Our test suite won't run when using
embroider
builds - the build completes but the tests never start.After the
Built project successfully
output, the process hangs indefinitely untilCtrl+C
is pressed. No tests are run.This issue happens when running
ember test
with the defaulttest
environment, which is why I opened a new issue instead of commenting on the production-specific https://github.com/embroider-build/embroider/issues/724