'Persistence 2.0' wont map right for the default angular-cli server (webpack)
Reported by
jniem...@warmlyyours.com,
Apr 12 2017
|
||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Mac Chrome version: 57.0.2987.133 (64-bit) What are the details of your project? - Build System: webpack / angular-cli@^1.0.0 - HTTP server: angular-cli ng serve Assets failed to link (or incorrectly linked): webpack:///./src/app/app.component.ts *should link to* file:///Users/jakeniemiec/RubymineProjects/_fire/src/app/app.component.ts _fire is the root project folder angular-cli does not allow you to edit any webpack config settings. Good thing I can map everything ok with the 'Persistence 2.0' experiment disabled. If possible, please attach a screenshot of network sources navigator which should show which resources failed to map
,
Dec 6 2017
Thanks for the report. Webpack changes the content of the sourcemaps resources, so the file on the file system (ile:///Users/jakeniemiec/RubymineProjects/_fire/src/app/app.component.ts) is not the same as the resource in the sourcemap (webpack:///./src/app/app.component.ts) This is a known issue with webpack; we can't do much here unfortunately. Closing this for now. |
||
►
Sign in to add a comment |
||
Comment 1 by pfeldman@chromium.org
, Apr 13 2017Status: Assigned (was: Unconfirmed)