chrome, source map not loading

Question

I am generating the bundled.js file using webpack for a typical angular project. Now I deploy this on the web server. The bundle.js file has the following at the end

//# sourceMappingURL=main.bundle.js.map

However Chrome does not seem to detect that there is a sourcemap available. It does not even show the icon saying that a source map is available. How do I fix this? Plus should the path to the sourcemap be http://url/main.bundle.js.map? How does chrome know where to load the sourcemap from?

**See Also**: [Sourcemaps are detected in chrome but original source is not loaded](https://stackoverflow.com/q/39146381/1366033) — KyleMit, Nov 01 '20 at 21:34

score 2 · Answer 1 · answered May 15 '22 at 19:59

2

For chrome, source-map was not loading/working for me too. I kept on seeing the bundle.js files. However, in other browsers it worked, that are chrome related like Brave. So I just went into my chrome browses dev-tools settings > preferences and then in the bottom right, I clicked the "Restore defaults and refresh" button and it worked fine after.

answered May 15 '22 at 19:59

V.Villacis

864
1
7
19

1

Not sure why it worked but it did, thank you! – Tekeste Kidanu Sep 30 '22 at 00:08

score -1 · Answer 2 · answered Sep 05 '17 at 16:37

-1

These are the runes you are looking for (chromeDevTools):

Map webpack://./ to /

answered Sep 05 '17 at 16:37

jake

488
10
19

3

Can you expand on this a bit @jake? What underlying problem does this solve? – Luke Griffiths Apr 29 '18 at 21:21
This tells chrome that the files under webpack's virtual directory should be mapped to your project directory. – jake Apr 30 '18 at 14:54

chrome, source map not loading

2 Answers2

Linked