source maps don't work for nodejs debugging via webpack
Reported by
joshung...@gmail.com,
Nov 13 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2916.0 Safari/537.36 Steps to reproduce the problem: I can't get source maps to work for nodejs debugging via webpack. They currently work for me on non-nodejs debugging. I also think WebStorm already supports source maps in this scenario. Maybe I'm missing a configuration step? 1. Save package.json, hello-world.js, webpack.config.js. 2. npm install 3. ./node_modules/.bin/webpack 4. node --inspect backend.js 5. Open URL in Chrome. 6. curl http://localhost:3000/ What is the expected behavior? Hello World prints to the console and shows the filename and line number of hello-world.js. I should also be able to set a breakpoint in hello-world.js. What went wrong? Hello World prints to the console and shows the filename and line number of backend.js. Can't set breakpoint. Did this work before? N/A Chrome version: 56.0.2916.0 Channel: n/a OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 24.0 r0
,
Nov 14 2016
,
Nov 14 2016
,
Nov 16 2016
Thanks for looking into it! Let me know if you're able to find any workarounds or need additional information.
,
Nov 18 2016
Related issue on the Node side: https://github.com/nodejs/node/issues/8369
,
Nov 18 2016
Note this issue could be split into two items if it is easier - 1. support inline source maps 2. support non-inline source maps
,
Oct 17 2017
This needs to be implemented on the node side (e.g. Node needs to provide source maps to devtools) |
||||
►
Sign in to add a comment |
||||
Comment 1 by joshung...@gmail.com
, Nov 13 2016732 bytes
732 bytes View Download