DevTools Node.js sourcemap support - source files not displayed
Reported by
m...@mattki.me,
Oct 21 2016
|
|||
Issue descriptionChrome Version : 54.0.2840.59 OS Version: OS X 10.12.0 What steps will reproduce the problem? 1. checkout https://github.com/mattkime/chrome-devtools-sourcemap-test 2. Open index.html in chrome and look at the console output and source list. The script will output '4' but more importantly you'll see index.es6.js in the source list. 3.Chrome DevTools sourcemap failure - Run npm start in the console and open the resulting url. Hit Resume on the debugger. The script will run to completion. Take a look at the source file list - index.es6.js is not present. What is the expected result? source files should be displayed when valid sourcemaps are provided. What happens instead of that? source files are not shown in the source list Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36
,
Oct 25 2016
Andrey, could you please take a look?
,
Dec 8 2016
This was a purely front-end issue, which was fixed: - https://codereview.chromium.org/2422803002 So as far as you use any more modern front-end, sourcemaps should just work. For example, navigating to the following URL will work just fine: chrome-devtools://devtools/remote/serve_file/@f43f91990836f23f5afe021685ca50f5236e924c/inspector.html?experiments=true&v8only=true&ws=localhost:9229/node
,
Dec 8 2016
In node 7, there's a different inspect link which refers to the bundled devtools front-end. In this case, sourcemaps should work just fine in Chrome 57 (which is current Canary)
,
Dec 9 2016
@lushnikov Is node v7 required for sourcemap support?
,
Dec 9 2016
@matt: it's either node7 + Canary, or you can use a custom inspect URL from comment #3. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ccameron@chromium.org
, Oct 25 2016Labels: -OS-Mac OS-All