Does not map local filesystem to webpack anymore with Workspace 2
Reported by
chris.pe...@gmail.com,
Dec 13 2017
|
||||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Win Chrome version: 63.0.3239.84 What are the details of your project? - Source code (if any): commercial - Build System: webpack - HTTP server: ng serve Assets failed to link (or incorrectly linked): The asset source maps point to webpack:///C:/Users/<myuser>/projects/.../mytypescriptfile.ts however DevTools > Settings > Workspace will only map between file:///C:/Users/<myuser>/projects/.../ to webpack:///C:/Users/<myuser>/projects/.../ and there is no buttons to link to webpack... also the previous map buttons have gone. So this feature is pretty useless. If possible, please attach a screenshot of network sources navigator which should show which resources failed to map
,
Dec 13 2017
I am seeing the same thing. I have a very easy repro for the issue: Just use create-react-app to quickly set up an example webpack app: https://github.com/facebookincubator/create-react-app Then start the example app with "npm start". Now try to set up a workspace mapping in DevTools. I can't get it to work no matter what I try. The "Establish the mapping now..." prompt pops up but does nothing, and auto-mapping doesn't happen. This is on Windows with Chrome 63.0.3239.84.
,
Dec 14 2017
,
Dec 16 2017
Also have troubles on Mac. Seems like with webpack 3 problem not happen. But it is look strange that webpack version matter.
,
Dec 20 2017
,
Jan 17 2018
I have the same result in Linux Chromium and Windows Chrome...
,
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 chris.pe...@gmail.com
, Dec 13 2017206 KB
206 KB View Download