Installing ember-fetch breaks source maps for prod builds about ember-fetch HOT 9 CLOSED

Under repo https://github.com/buschtoens/ember-fetch-sourcemap-bug

rm yarn.lock
yarn install
ember b -prod

No more Building[WARN] (broccoli-uglify-sourcemap) "ember-fetch.map" referenced in "assets/vendor.js" could not be found

from ember-fetch.

The problem was introduced with v4.0.0.

While warning about deprecations, the source map gets built correctly:

yarn add -D 'ember-fetch@<4' && ember build -prod && head -c 500 ./dist/assets/vendor*.map

from ember-fetch.

Which is weird, because according to v3.4.4...v4.0.0 there is no difference between v3.4.5 and v4.0.0. 🤔

from ember-fetch.

Oops, it's not v3.4.4...v4.0.0. I was tired yesterday, sorry 😄. Looking for the right version now.

from ember-fetch.

It's v4.0.0...v4.0.1.

Works:

yarn add -D [email protected] && ember build -prod && head -c 500 ./dist/assets/vendor*.map

Breaks:

yarn add -D [email protected] && ember build -prod && head -c 500 ./dist/assets/vendor*.map

Therefore #112 (#111) bricked it. 🙁

from ember-fetch.

broccoli-concat by default creates a source map and injects a sourceMappingURL comment into the file. When the file is eventually concatenated into vendor.js, something goes wrong and the sourceMappingURL is not processed and just stays as it is.

This means that later, when broccoli-uglify-sourcemap (L31) processes vendor.js, it finds the rogue sourceMappingURL comment and tries to load the ember-fetch.map, which of course at that point is not part of the tree anymore.

One possible fix is passing sourceMapConfig: { enabled: false } to broccoli-concat to disable source map generation and thus removing the sourceMappingURL comment.

from ember-fetch.

I guess the file ends up here and broccoli-concat itself is probably not aware of source maps when joining files.

So I guess passing sourceMapConfig: { enabled: false } is indeed the correct solution to this problem.

from ember-fetch.

@stefanpenner @tchak see comment here broccolijs/broccoli-concat#123 (comment)
Any thoughts about this?

from ember-fetch.

So the solution here was to nuke the yarn.lock file? 🤣

from ember-fetch.