microsoft/vscode-chrome-debug-core

Node debugger in VS not stopping on breakpoints when project is loaded from a network share

Shenniey opened this issue · 2 comments

When attempting to debug a Node project in Visual Studio that is loaded from a network share, breakpoints that are set are not bound, and therefore not being hit.

I believe the error is due to a mismatch in the filepath representation. I've attached one run of the logs below. In the SetBreakpoints method it is looking for a path with two leading backslashes, with directories indicated by backslashes. However when the scripts are loaded, it has a single forward slash in the beginning, and lower directories are also indicated by forward slashes.

This issue is due to the bug that was filed here. More details are given in the bug link.

Here are the modified log files (I changed some things in case they had private info).
dev16 log output from NETWORK SHARE.txt

I can repro in vscode

I think I've fixed it.