Repository navigation
Support Ember 4.x / ember-auto-import 2.x #4179
Description
Hey folks.
We are currently investigating supporting Ember 4.x and ember-auto-import 2.x. This is a breaking change for our package, so we are exploring the best way to proceed with it.
As we make progress, we will update this issue with details. Thank you!
See some related issues:
Activity
fix(ci): Temporarily allow `ember-release` tests to fail in CI (#4227)
Emerson commentedon Dec 9, 2021
Eager to hear more about this issue. I'm trying to prepare our applications for Ember v4 and this is one of the things that's holding me back.
AbhiPrasad commentedon Dec 9, 2021
Actually @Emerson it seems that #4253 might just get things to work without having to have a breaking change due to how we use ember auto import
We are doing some investigating now, keep an eye on that GH issue!
Emerson commentedon Dec 9, 2021
Awesome, I'll be watching 👁️
fix(ci): Temporarily allow `ember-release` tests to fail in CI (#4227)
Emerson commentedon Jan 5, 2022
Just a heads up - tried to update to
ember-auto-importtov2.2.4and pulled down the latest@ember/sentrytov6.16.1and I'm still getting this error in production. I also have an issue open withember-auto-importhere
.Emerson commentedon Jan 5, 2022
Looking at this in more detail and it may be related to my own config. I'll look into it and report back.
Emerson commentedon Jan 5, 2022
Ok, this was my own config issue. Please disregard my nonsense. 🤦
vladanpaunovic commentedon Jun 8, 2022
It seems like this was resolved in #4253. @AbhiPrasad, do we still need this issue?
AbhiPrasad commentedon Jun 8, 2022
Yeah we can close.
pomm0 commentedon Jul 22, 2022
@Emerson I'm also seeing this error, can you please share how you fixed it?
(just a mention of the error to make it searchable)
Edit:
Well, wrong usage of
publicAssetURLwas the issue (missed the trailing/assetscompared to thefingerprint.prependurl)