Chrome devtools source map has problems
Reported by
mon...@gmail.com,
Jan 11 2018
|
||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Windows 10 64bit Chrome version: 63.0.3239.132 (64bit) What are the details of your project? - Source code (if any): http://localhost:7073/... - Build System: maven - HTTP server: tomcat Assets failed to link (or incorrectly linked): 1. at first, mapped to maven build target instead src. so, after I add '/target/' to Folder Exclude Pattern, mapped to src. 2. My project have linked source, (Symbolic link using 'mklink /J ...' command) but it's not mapped ... 3. I developed javascript logger, and it's source link have worked fine at previous version. But now it doesn't work... for example, in my logger library write console.log('http://localhost:7073/aaa/bbb.js') and click the line, it shows network source in new tab. (in some previous version, it open mapped source in dev tools)
,
Dec 8
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story. |
||
►
Sign in to add a comment |
||
Comment 1 by eostroukhov@chromium.org
, Jan 11 2018Status: Assigned (was: Unconfirmed)