unable to add directories from webpack (where the breakpoints will work) in devtools
Reported by
brian.le...@gmail.com,
Mar 22 2018
|
|||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Linux Chrome version: 64.0.3282.186 (Official Build) (64-bit) What are the details of your project? - Source code (if any): Angular - Build System: Webpack - HTTP server: node HTTP Assets failed to link (or incorrectly linked): 1. webpack:// I am unable to get my project files to map to a workspace. I used to be able to add these folders and use breakpoints within them. Now, the right-click option of "add folder to workspace" doesn't show up for folders coming from the "webpack://" directory. If I go to the filesystem tab, I am able to add these folders from the filesystem, although breakpoints do not work within these files. The only place breakpoints work are in files from the "webpack://" directory, although this file tree closes with each page refresh. The file will stay open, but this makes it difficult to navigate between multiple files if I don't want them all open at the same time. This is not the behavior that I expect. I used to be able to add folders from webpack to the workspace and have them persist between page refreshes and also use breakpoints within them.
,
Apr 3 2018
,
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 susan.boorgula@chromium.org
, Mar 23 2018