VSCode Javascript Debugger doesn't hit the breakpoint after few code changes

[middiu]

VSCode Javascript Debugger doesn't hit the breakpoint after few code chjanges.

Steps to Reproduce:

1. Create a new ReactJS project
2. Create a launch json file for setting the chrome debugger
3. Start the browser, do a change in you editor, add a new line, add a breakpoint, save it(you might need to repeat this step for 2-3 times but usually reproduces after the first save)
4. After the file is saved and the browser refreshes you will observe that your breakpoint will not hit anymore, seems to be a caching issue, after the browser will be restarted then the breakpoint will hit, the dev tools are showing the correct source code.
5. This worked since a 2-3 weeks ago (I've been on away and didn't code for few weeks)

Other people are facing the issue it seems: microsoft/vscode#189863

Log File
vscode-debugadapter-affae410.json.gz

Version: 1.82.1 (user setup)
Commit: 6509174151d557a81c9d0b5f8a5a1e9274db5585
Date: 2023-09-08T08:45:05.575Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19044

[middiu]

Just updated to latest vs code and the issue is still there.
I also tried with latest Chrome version as well as Chromium, same problem.

Version: 1.82.2 (user setup)
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:55:25.390Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19044

[middiu]

Tested on my Mac on a different ReactJS project and got the same problem, after few app changes the breakpoint is not hit:

Version: 1.82.2
Commit: microsoft/vscode@abd2f3d
Date: 2023-09-14T05:59:47.790Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin x64 22.6.0

[CaidenKehrer]

I can second this issue

Version: 1.84.0-insider (user setup)
Commit: 901ac65ea9f906d6996ad8e7639ba81acecf1d7c
Date: 2023-10-12T05:37:35.298Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

Using
Angular 15.2.9

If there is any way I can help get this fixed it is a major slowdown for debugging any related issues.

[CaidenKehrer]

For anyone that is having an issue the same way I am. Here are the tests I ran.
I tested it on edge and chrome.
I ran ng serve with the source map enabled.
I verified that my configuration included source maps.
I ran with trace enabled and tried to see if any issue arose in the console.

Preface warning: I am not recommending that people do this.
The only fix I found was disabling this extension, going to the deprecated Debugger for chrome extension, and installing the vsdx manually. Then configuring it to use that as the debugger. I will be using the deprecated chrome debugger extension until this is fixed. (I am willing to reinstall the js-debug extension if help is needed solving this issue)

[connor4312]

Please try the next nightly build after 5PM PST today for the fix.

Not sure why this just came up, this should have been a problem for the last couple years since we added sourcemap caching 🤔