Unbound breakpoint when Debug: Open Link command is used

[jkohlin]

Describe the bug
When trying the new feature Debug: Open Link command in VS Code 1.48, red breakpoints turns into a white oulined breakpoint with the tooltip "Unbound breakpoint". The problem then is that the code doesn't break at the breakpoint and hence won't let me debug the code in VS code.
I'm running a local server via a npm run dev script cross-env NODE_ENV=development webpack-dev-server --open --inline --hot

To Reproduce
Steps to reproduce the behavior:

1. copy your localhost url
2. open Command palette
3. Type debug: open link and press Enter
4. open a js file and click in the line number gutter to add a breakpoint

Log File

VS Code Version: 1.48.0

Additional context
Running on a Mac with MacOS 10.15.6

[connor4312]

Thanks for the issue. Do you already having a launch config for your project? If so, and if you've applied any changes or configuration to that, you may need to also set them in the link debugging mode (via the setting debug.javascript.debugByLinkOptions).

If not, please collect a trace log using the instructions in the issue template and I'll be happy to figure out what's wrong 🙂

[jkohlin]

Do you already having a launch config for your project? If so, and if you've applied any changes or configuration to that

I don't think I have any launch config for my project, and wouldn't know what to put in debug.javascript.debugByLinkOptions. Where do I add "trace": true?

[jkohlin]

Is this how I do that?

[connor4312]

Adding "debug.javascript.debugByLinkOptions": { "trace": true } to your settings

[jkohlin]

Here's the log file: vscode-debugadapter-4.json.gz

Strangely it works intermittently, I just can't figure out why. This log is from one of those non successful times

[connor4312]

It looks like you're debugging a Vue up. Currently, they don't generate sourcemaps that we can reliably map back to the source files. I've opened vuejs/vue#11023 on them to try to improve this. Once that happens we will be able to make breakpoints work reliably.

[bartocc]

vscode: Version: 1.50.1
js-debug-nightly: v2020.10.1317

---

I've just hit what looks like to be the same issue, with the difference that my breakpoints bound when using Debug: Open Link from the command palette and not bound when cmd+clicking a URL in the terminal (normal or js debug terminal)

I've got the following launch.json file, and breakpoints are correctly bound when debugging with it:

{
  "configurations": [
    {
      "name": "Launch Chrome",
      "type": "pwa-chrome",
      "request": "launch",
      "url": "http://localhost:4200",
      "sourceMapPathOverrides": {
        "ember-cli-babel-sourcemap-bug/*": "${workspaceFolder}/app/*"
      }
    }
  ]

}

and the following settings.json file:

{
  "debug.javascript.debugByLinkOptions": {
    "trace": true,
    "enabled": "always",
    "sourceMapPathOverrides": {
      "ember-cli-babel-sourcemap-bug/*": "${workspaceFolder}/app/*"
    }
  }
}

Any idea why cmd+click fails ?

Here's the trace after a cmd+click :
vscode-debugadapter-6.json.gz