Can't use client debugger on minified bundle.

[davidkellerman]

[Okay, read all the way to the bottom; I've been amending this as I poke around.]

The bundled output from clientjs is minified (as one very long line), which means debugging anything in the bundle using the browser debugger is not possible. Certainly, during development at least, un-minified output should be the default.

Setting "minify": false in the client_js configuration isn't helpful. What is then visible in the browser debugger is webpack's stringified output. (Which the Chrome debugger handles badly, tending to freeze when searching it, for example.)

Okay, one more update. The expanded code modules appear in the Chrome debugger in the Sources list under webpack://. Figuring out how things are arranged may take some getting used to, but so far things seem to be there.

[loppear]

Yeah, I think sourcemaps have to be the answer regardless, open question is probably whether the default choice of source map approach is as useful as it could be (https://webpack.js.org/configuration/devtool/#devtool) - for dev I'm using cheap-module-eval-source-map and for production source-map.