Alex
Alex
I will add that the same result is visible with a 3.28 app once upgraded to auto-import v2.* but not visible with auto-import v1 also still investigating but there may...
> @bertdeblock Because testing production builds is a thing everyone should do (though most don't and I mostly see only addons do this) I get that, but how does one...
for us it's added into the index.html by the ember cli build process so it's always requested default `npm run build` script thinking it's got something to do with using...
> Could it be that maybe you are importing/including test-related code in the app itself somehow? With a fresh app, I only observed the chunk being made, but _not_ included...
so turns out (as far as I can tell) ember-auto-import@2 is behaving correctly and the miragejs and faker packages appearing in the scripts added to the html is due to...
hasn't this already been done on https://github.com/ember-cli/ember-fetch/pull/741 ?
@colenso are you not able to use https://github.com/embroider-build/embroider/tree/main/packages/macros#istesting-isdevelopingapp macros?
hello @NagarajNN a few things to check: * does it happen with the normal ember router * Which version of the embroider router is this * is it on load...
are you able to create a minimal reproduction of what you're seeing, as that would greatly help in fixing this
I would ask you to try and narrow down where this is coming from, is the dynamic segment properly url encoded? I know FF/safari is less error tolerant than chrome...