Breakpoints are no longer hit when using the latest chrome debugger in vscode
See original GitHub issueDescribe the bug
Breakpoints are no longer hit when using the latest chrome debugger in vscode. This could be due to using symlinked folders in projects (where this bug has been encountered)
To Reproduce
- Use a project which relies on symlinks in the source (e.g. a monorepo with hoisted libraries)
- Set a breakpoint in the source
- Use the latest chrome debugger with a
launch
config - Launch and debug the project
Log File Attached:
vscode-chrome-debug.working.txt vscode-debugadapter-2.failing.json.gz
VS Code Version: 1.48.0
Additional context
Chrome debugger: Version: 4.12.10
macOS: 10.14.5
Works correctly when setting debug.javascript.usePreview
to false (no longer the default)
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Visual Studio Code debugging chrome, Breakpoints wont hit
Setting the workspace location to the location of my typescript files, and not my build files, worked for me. Unverified Breakpoint (my ...
Read more >Solve “Breakpoint ignored” with Visual Studio code (vscode ...
Breakpoints may still not trigger on initial load. When you start the debugger which launches Chrome, there is a lag before vscode can...
Read more >Breakpoints lost on refresh #1219 - microsoft/vscode-js-debug
Launch Chrome debug session; Set breakpoint; Execute action to hit breakpoint; Breakpoint activates and pauses execution; Unpause debugger; Refresh page ...
Read more >Debugging in Visual Studio Code
One of the great things in Visual Studio Code is debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >Easier browser debugging with Developer Tools integration in ...
To debug any project in either Chrome or Microsoft Edge, all you need to do is to start a session by pressing F5...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve added a default to handle absolute paths like this, in the linked commit
As this is a regression / change in behaviour, perhaps it should be documented?