Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node.js breakpoints become "unbound breakpoint"

See original GitHub issue

Describe the bug node.js breakpoints become “unbound breakpoint”.

To Reproduce Steps to reproduce the behavior: After upgrade to 1.47, just open my node.js project, and start debugging, all breakpoints said to be “unbound breakpoints”

Log File

VS Code Version: 1.47

Additional context I revert to 1.46, all breakpoints works well

Issue Analytics

State:
Created 3 years ago
Comments:14 (7 by maintainers)

Top GitHub Comments

1reaction

offerocommented, Sep 1, 2021

I’m having the same issue now. VSCode Insiders 1.60.0-insider Node 8.15 application I used to be able to set breakpoints okay. I seemingly cannot switch back to the old debugger; the config option is no longer available.

1reaction

connor4312commented, Jul 11, 2020

Can you please share the log file using these instructions?

If you’re able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you’d rather not share the log publicly, you can email it to connor@xbox.com