Hi there!

Using Webpack 1.5.3 and Chrome 40 (not Chrome 39, it works properly), open a page with a javascript error and click on one of the links in the backtrace for that error. (In a file from the Webpack bundle, of course).

If your experience is like mine, a new blank tab will pop up with the URL that devtools should be using to navigate to the source inside of bundle.js.

when the devtool string in the webpack config is set to '#inline-source-map' Chrome understands the link just fine, but there have been reports of reduced accuracy in line numbers with that method, and also the filename in the backtrace is always 'bundle.js'. '#eval' seems to be more accurate, and it shows original filenames in the backtrace, but clicking on that backtrace link breaks in Chrome 40.

I'm opening up this issue here not because this is necessarily a webpack issue, but because I thought it'd be a good place to get ideas about what could be going wrong.

Any ideas? :)