breakpoints not hit when serving project from wsl

[mirronelli]

• VS Code Version: 1.40
• Extension version: 1.0.12
• Log file (only the important part I believe, more can be supplied if needed):

  From client: setBreakpoints({"source":{"name":"App.vue","path":"vscode-remote://wsl%2Bubuntu-18.04/home/mirronelli/code/vue/neo/src/App.vue"},"lines":[33,39,40,41],"breakpoints":[{"line":33},{"line":39},{"line":40},{"line":41}],"sourceModified":false})
  To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"setBreakpointsRequest","data":{"Versions.DebugAdapterCore":"6.7.48","Versions.DebugAdapter":"1.0.12","Versions.Target.CRDPVersion":"1.3","Versions.Target.Revision":"@798239fe3bf48be032a1b7009ff3f04ce7158c26","Versions.Target.UserAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3952.0 Safari/537.36 Edg/80.0.320.5","Versions.Target.V8":"8.0.89","Versions.Target.Project":"Edg","Versions.Target.Version":"80.0.320.5","fileExt":".vue"}}}
  SourceMaps.setBP: vscode-remote://wsl%2Bubuntu-18.04/home/mirronelli/code/vue/neo/src/App.vue can't be resolved to a loaded script. It may just not be loaded yet.
  Paths.setBP: vscode-remote://wsl%2Bubuntu-18.04/home/mirronelli/code/vue/neo/src/App.vue is already a URL
  To client: {"seq":0,"type":"response","request_seq":33,"command":"setBreakpoints","success":true,"body":{"breakpoints":[{"id":1012,"verified":false,"message":"Breakpoint set but not yet bound"},{"id":1013,"verified":false,"message":"Breakpoint set but not yet bound"},{"id":1014,"verified":false,"message":"Breakpoint set but not yet bound"},{"id":1015,"verified":false,"message":"Breakpoint set but not yet bound"}]}}
  To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"ClientRequest/setBreakpoints","data":{"Versions.DebugAdapterCore":"6.7.48","Versions.DebugAdapter":"1.0.12","Versions.Target.CRDPVersion":"1.3","Versions.Target.Revision":"@798239fe3bf48be032a1b7009ff3f04ce7158c26","Versions.Target.UserAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3952.0 Safari/537.36 Edg/80.0.320.5","Versions.Target.V8":"8.0.89","Versions.Target.Project":"Edg","Versions.Target.Version":"80.0.320.5","successful":"true","timeTakenInMilliseconds":"1.327699","requestType":"request"}}}

Steps to reproduce:

1. create a vue cli project hosted on a wsl 1 ubuntu node
2. execute: npm run serve
3. launch debugger from the launch.js as described here in readme.md
4. set a breakpoint into whichever file (even main.ts or app.vue)

The debugger attaches to the browser and the console output is being displayed in vscode as expected. However the sourcemaps do not hit locally set breakpoints. When running using trace='verbose' it seems the vscode is sending a wrongly formatted path to the browser to match against its paths. See the output above.

I believe the '''vscode-remote://wsl%2Bubuntu-18.04''' part of the path is what confuses edge, since it knows nothing about the files being hosted on such a path (wsl).

The equivalent extension for chrome works as expected on the same setup and using the same settings, apart from the executable and version parameters.

[lgp1985]

I had the same issue, one way around should be to run the extension from the workspace. Define in your settings.json

{
    "remote.extensionKind": {
        "msjsdiag.debugger-for-edge": [
            "workspace"
        ]
    }
}

Then you'll need to install the extension also there (on your WSL). After you'll need to define in your project .vscode/launch.json the path to your host msedge.

{
    "configurations": [
        {
            "type": "edge",
            "request": "launch",
            "name": "Launch Edge",
            "url": "http://localhost:3000/",
            "webRoot": "${workspaceFolder}/",
            "runtimeExecutable": "/mnt/c/Program Files (x86)/Microsoft/Edge/Application/msedge.exe",
            "runtimeArgs": [
                "--remote-debugging-port=2015"
            ],
            "skipFiles": [
                "<node_internals>/**"
            ]
        }
    ]
}

This should make your breakpoints work once launched. If you made any mistakes, you'll see when mouse over Breakpoint set but not yet bound