Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

web pack source map not working for some devtool options.

See original GitHub issue

Do you want to request a feature or report a bug? bug

What is the current behavior? Sourcemap is not working for some devtool options. Tested options: eval: working cheap-eval-source-map: working cheap-source-map: not working cheap-module-eval-source-map: working cheap-module-source-map: not working source-map: not working inline-source-map: not working hidden-source-map: not working nosources-source-map: not working

If the current behavior is a bug, please provide the steps to reproduce.

I reproduced the bug in this repo: https://github.com/SemihGk/waka-player npm install -> npm run prod -> watch console messages in localhost:3000

It’s really a weird issue. I am not sure any plugin causes this error. I do not think so. Just in case, you may check that in the repo. It is very basic sample repo and just used a couple webpack plugins such as html-webpack-plugin and copy-webpack-plugin. You can find those plugins’ versions in package.json file. I suspect the compatibility between webpack and babel-loader.

What is the expected behavior? source map should work in all devtool options.

If this is a feature request, what is motivation or use case for changing the behavior? It’s bug.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

“webpack”: “^3.5.1”, Mac OS: 10.12.6 node: 8.2.1 Tested on Chrome 60, Mozilla 54, Safari 10.1

Issue Analytics

State:
Created 6 years ago
Reactions:42
Comments:28 (1 by maintainers)

Top GitHub Comments

7reactions

nelsonomutocommented, Jul 5, 2018

Same thing here, can’t get any sourcemaps other than *-eval-* sourcemaps to work 😡

7reactions

cloakedninjascommented, Jun 27, 2018

For some reason, not sure why, we’ve run into this bug too, will migrating to Webpack 4 fix this ?

But our SCSS sourcemaps generated by gulp-sourcemaps are working fine, which makes me think this isn’t a Chrome issue

Update: Do make sure they’re not disabled in Chrome 🤦‍♂️
screen shot 2018-06-27 at 17 03 01

Top Results From Across the Web

Source Maps not working with Webpack - Stack Overflow

I'm pretty new to webpack and having some trouble configuring it to produce the necessary source maps. In the devtools it says.

Devtool - webpack

devtool performance production quality (none) build: fastest rebuild: fastest yes bundle eval build: fast rebuild: fastest no generated eval‑cheap‑source‑map build: ok rebuild: fast no transformed

[Fixed] Webpack problem with source maps mapping in ...

[Fixed] Webpack problem with source maps mapping in Chrome Dev Tools. I find it essential to be able to edit the code directly...

4 Reasons Why Your Source Maps are Broken - Sentry Blog

Here are four reasons why your source maps are broken and tips on how to ... Using Webpack, specifying devtool: "source-map" in your...

Quick guide to webpack source map options - Scott Logic Blog

The webpack devtool configuration option controls source map ... or a reporting service) should be of use to us in diagnosing problems ......