chrome://inspect devtools does not interact with WSL when displaying files
Reported by
paulfris...@gmail.com,
Sep 20
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. start a nodejs server via bash on WSL (windows subsystem for linux) 2. go to chrome://inspect and click 3. click on the Sources tab in the devtools What is the expected behavior? You can see and navigate all source files that the server is using. What went wrong? The devtools know that server.js is at file:///mnt/c/Users/.../Documents/.../server.js but it cannot do anything with this information. It does know about the WSL filesystem. Did this work before? No Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version: This would be a nice accessibility feature.
,
Sep 21
,
Sep 24
Could you attach a screenshot of Sources panel?
,
Sep 24
hmm it seems to work now, at least it is doing the same as happens when I work with the Windows version of node Initially, there will be no files and then I can click on a filename that is displayed e.g. after a log entry and it will open the file The only difference is that "Open in containing folder" does not work with the WSL (windows subsystem for linux) version of node... |
||
►
Sign in to add a comment |
||
Comment 1 by susan.boorgula@chromium.org
, Sep 20