Closed sonikro closed 3 weeks ago
https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_how-can-i-set-nodeoptions
Damn that was a fast reply. That was exactly the problem. I failed to realize that by overriding NODE_OPTIONS, it would impact the Node debugger.
Changed it to:
NODE_OPTIONS=\"$NODE_OPTIONS --no-node-snapshot\"
And the debugger is working again as intended.
Thanks
Does this issue occur when all extensions are disabled?: Yes
Version: 1.94.2 (system setup) Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427 Date: 2024-10-09T16:08:44.566Z Electron: 30.5.1 ElectronBuildId: 10262041 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.19045
Steps to Reproduce:
It is possible to debug with --no-node-snapshot IF i use --inspect-brk, and then Attach to Process. When I do that, I can debug the process even with --no-node-snapshot.
Traces
Traces of when running the normal process:
Traces for when running with --no-node-snapshot
Here is my launch.json