16

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?

Improve this question
1

2 Answers 2

Reset to default
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.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Not sure why it worked but it did, thank you!
In those dev-tools settings>preferences, there's a checkbox "Javascript source maps". Somehow this was disabled in my case. Just enabling that was enough - I didn't have to restore the defaults.
-1

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

Map webpack://./ to /

enter image description here

Improve this answer

2 Comments

Can you expand on this a bit @jake? What underlying problem does this solve?
This tells chrome that the files under webpack's virtual directory should be mapped to your project directory.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.