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.
Unbound breakpoint when Debug: Open Link command is used
See original GitHub issueDescribe 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:
- copy your localhost url
- open Command palette
- Type debug: open link and press Enter
- 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
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
And I confirm it is now working with
v2020.10.1517awesome 👍