Node Debugger not working after updating to June 2020 (version 1.47)
See original GitHub issueDescribe the bug Node Debugger not working after updating to June 2020 (version 1.47)
To Reproduce Steps to reproduce the behavior: After update when I tried to run a server in debug mode it shows me the “options [retryMiliSeconds] is not supported”. Server gets started but debugger points gets disappeared.
Log File
VS Code Version: Replace me!
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:18 (10 by maintainers)
Top Results From Across the Web
June 2020 (version 1.47) - Visual Studio Code
Welcome to the June 2020 release of Visual Studio Code. There are a number of updates in this version that we hope you...
Read more >New JavaScript Debugger Now Default in VS Code 1.47 ...
New JavaScript Debugger Now Default in VS Code 1.47 (June 2020 Release) · Single file debugging: · Less cluttered CALL STACK view: ·...
Read more >Software-update: Visual Studio Code 1.47.2 - Tweakers
Extensions issues after update to vscode 1.47.0 · [node-debugger] Debugger spams "Could not read sourcemaps" messages · Node version detection ...
Read more >VS Code Debugging problems after last update (1.69.2)
I think there is a problem with the latest version. So try using the previous version. I'm sure the VSCode team is working...
Read more >Visual Studio Code 1.74.1 (64-bit) Download for ... - FileHorse
Zsh history not working after update ... Node JS Debugger Error ... VS Code pre-release does not reload code on restart of the...
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
Thanks for the log!
I think I already fixed your issue as part of https://github.com/microsoft/vscode-js-debug/commit/540fbcace9eda0c43fa0b73797d3cba95a2f443b. I think both of these solutions will work for you:
--inspect-brk
from your npm script (we can attach without it; I’ve updated the docs to reflect that in https://github.com/microsoft/vscode-docs/commit/26b07f527e9862827492aa8fb604dec13a5ef824)That issue should be fixed as of VS Code 1.47.2. If you’re still seeing it, can you collect a trace log using these steps? https://github.com/microsoft/vscode-js-debug/issues/631#issuecomment-660149131