Breakpoints open read-only file

• VS Code Version:
• Log file (set "trace": true in launch config):

Steps to reproduce:

1. Have generic launch.json config like

{
      "type": "pwa-chrome",
      "request": "launch",
      "name": "Launch Chrome debug",
      "url": "http://localhost:8080",
      "webRoot": "${workspaceFolder}",
      "disableNetworkCache": true,
      "runtimeArgs": ["--incognito"],
}

1. Have VSCode Chrome Debugger extension enabled
2. Set breakpoint (or add debugger) anywhere in your code
3. Use website to hit the breakpoint
4. VSCode opens new read-only file that has similar path to the original, has all same breakpoints, but is read-only. Although one thing to note is read-only file path starts with ~/Desktop while for original VSCode shows /home/myUser/Desktop

System is: Ubuntu 19.10 Node v12.8.1 VSCode v1.45.1 Debugger for Chrome v4.12.7

Files are converted and served with Webpack and webpack-plugin-serve

Expected behaviour: Debugger continues to use same file with full edit support

Edit: https://github.com/VandalPaulius/code-examples I’ve created example repository for this

[VandalPaulius]

Thanks for checking it 💯 Yes, I got it working just now. Was about write it in here. As always it was user error 😄 As you said it was sourcemap and webroot config issue. I will keep this repo on, so anyone that comes to this problem has some reference (even though setup in that repo is a bit unconventional)

[connor4312]

Please open a new issue and fill in the template @Slos https://github.com/microsoft/vscode-js-debug/issues/new/choose