I am having the same problem right now. Eval source maps work fine.

Webpack: ^2.2.0
Chrome: 60.0.3112.101 (Official Build) (64-bit)
OSX: 10.12.6

Also experiencing this issue:

Webpack: 3.3.0
Chrome: Version 60.0.3112.101 (Official Build) (64-bit)

I've explored this further and my sourcemaps are working as expected in Firefox. Just not in Chrome.

is that a similar issue to this? #5569 (comment)

@MACSkeptic . Not really. I did not even specify UglifyJsPlugin in my config. Sourcemap is just not working properly when multiple entries are set to webpack. @petermikitsh , I still have the issue in Chrome, Firefox and Safari. That's interesting. Could you provide a sample repo? Maybe, I can test it as well and I can see that is it the same issue that I have?

#5569 provide a very simple sample repo. You can see it in it.
I'm the issuer. It seems that the webpack owner has no time to deal with the bug or he thinks it's NOT a bug. He may think we just use it in a wrong way , however it's obviouse that the bug is not reasonable. Now I feel frustrated.

I tested your project. It seemed no bug.
Browser: Chrome version: 59.0.3071.86
Operating system: windows 7 64bit

And I updated the chrome to the newest version (60.0.3112.113). It still worked fine.
And the configuration is devtool: 'source-map',

Hey @yincu . It is already marked as an important bug. You cannot expect them to fix the bug right away as there are tons of bugs are on their list.

As I described in my first message, watch console.logs carefully. Otherwise, sourcemaps files are already created.

I just cloned my repo and did run it again. It is still a clear bug as you may see in the screenshot. Expecting behavior is that show the exact file and line. Not the bundled file. How about your console?

I get what you said. I reproduced the bug. However, it seems it may be a browser bug of chrome or it's NOT a bug.
When you browser http://localhost:3000/ page without a devtool window displayed. You'll get the right source map. Or if you get what you got in your above post picture. You can close the devtool window of chrome and open it again. Boom! You get what you want.

The source map files will not be get from the server unless you reopen the devtool window. These files are not expected to be acccesed by users when browsering the pages. They will not be downloaded along with the js or css files.
These files will only be downloaded and parsed when the devtool window is reopened.

It might be a browser bug, but it happens in other 3 browsers as well. Plus, it works fine with some other sourcemap types. Besides, it works as well if I assign only one entry to be bundled. I am not an expert and I cannot speak in a certain way, but it seems this bug is more related to webpack.

You could test this way with other sourcemap types to see if it works the same.
The test with the configuration devtool: 'source-map' suggests that it has nothing to do with webpack.

Source maps are used for debugging. The behavior of Chrome is reasonable .

Got the same issue, eval config works.

Also this problem, auto source map not work in chrome canary with webpack.

Hi is there a workaround for this? For me devtool: 'inline-source-map' works but devtool: 'source-map' does not. It produces an nearly empty source map.

@SemihGk I had a similar issue and was able to resolve this by reading through #5569 (comment) and changing the -d (dev flag) to -p

  "scripts": {
    "start": "node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js -p",
    "clean-js": "rm -rf ./dist/js",
    "quality": "eslint",
    "build": "webpack",
    "build-prod": "webpack --config webpack-production.config.js -p",
    "test": "node scripts/test.js --env=jsdom"
  },

Facing the same problem, it is uglifying when not told to and not having the devtool source map in cheap-source-map, source-map or any devtool option like inline-source-map.

Update: Just fixed it using mode in webpack 4

@devssh so you get sourcemaps even with devtool: "source-map", or what?
Can you post your webpack config?

Yes here is my baseConfig

const path = require('path');
const webpack = require('webpack');

module.exports = {
  devtool: 'cheap-module-source-map',
  entry: ['./client/src/index.js'],
  output: {
    path: path.join(__dirname, '../server/public'),
    filename: 'static/bundle.js',
    publicPath: '/'
  },
  plugins: [
    new webpack.DefinePlugin({
      'HOST_MACHINE_URL': JSON.stringify(process.env.HOST_URL)
    }),
    new webpack.NoEmitOnErrorsPlugin()
  ],
  module: {
    rules: [
      {
        test: /.html$/,
        loaders: "html-loader"
      },
      {
        test: /\.(js)$/,
        exclude: /node_modules/,
        use: ['babel-loader']
      },
      {
        test: /\.(scss|css)$/,
        use: ["style-loader", "css-loader", "sass-loader"]
      },
      {
        test: /\.(eot|ttf|woff2|woff|jpg|png|svg)(\?[a-z0-9]+)?$/,
        use: [{
          loader:'file-loader',
          options: {
            name: '[name].[ext]',
            outputPath: 'static/',    // where the fonts will go
            publicPath: '/'       // override the default path
          }
        }]
      }
    ],
  }
};

Now in the dev server

const baseConfig = require('./webpack.base.conf');
const webpack = require('webpack');

console.log(baseConfig.entry.push.apply(baseConfig.entry, [
  'webpack-hot-middleware/client?reload=true',
  'react-hot-loader/patch'
]));

baseConfig.entry.reverse();
baseConfig.plugins.push.apply(baseConfig.plugins, [
  new webpack.NamedModulesPlugin(),
  new webpack.HotModuleReplacementPlugin(),
]);

baseConfig.devServer = {
  hot: true
};

module.exports = baseConfig;

What was added to fix the issue was

baseConfig.mode = 'development';

and it happened because we migrated from Webpack 3 to Webpack 4

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 🤦‍♂️

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

If the script is within an iframe, you have to enable "Search in anonymous and content scripts" in Chrome.

Using webpack 4 with source-map option. It work in 20% of cases, even don't know how to reproduce it. Previously I use gulp, and gulp put source maps inside of js bundle. Webpack put source maps as separated file, think it is a root problem. Will try something like 'cheap-eval-source-map', hope it will help (latest version of chrome).

I had the same problem in chrome, but it worked in firefox

Fixed in webpack@4, Firefox has some problems with source maps, here more information #1194 (fixed in nightly)

I want to close this issue, because it is fixed, but if you faced with the problem again, feel free to open a new issue with reproducible test repo, we have many tests on source maps

Running on webpack==4.41.2, the fix for me was setting sourceMap: true for the TerserPlugin, as the docs highlight:

    sourceMap: true, // Must be set to true if using source-maps in production

This change meant I started to get source maps for all the available devtool values, not just the eval* ones.

Webpack 5 loses support for sourceMap: true
Terser Plugin 5.0.0 release Notes
What is the equivalent option for webpack5?