Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
When using any devtool strategy that uses eval, such as cheap-module-eval-source-map, the browser developer tools show two sets of files with quasi-identical names. The first set under the webpack:// origin contains original sources. The second set under webpack-internal:// origin contains transpiled sources.
Note that this has changed in webpack 4. In the previous version that webpack-internal:// files used numeric identifiers, so there was no risk to open them by accident and they did not show up when using Ctrl+P in Chrome.
If the current behavior is a bug, please provide the steps to reproduce.
git clone https://github.com/lorenzodallavecchia/webpack-bug-duplicatesource.git
cd webpack-bug-duplicatesource
npm install
npm start
What is the expected behavior?
I would expect to only see original sources (under webpack://) or at least give the “internal” sources a numeric identifier so that they do not show up when searching with Ctrl+P.
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
webpack 4
Node 6.11.0
Chrome 65
Windows 10 1709
optimization.namedModules: falseshould do the trick.