Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New JavaScript Debugger stuck since VS Code version 1.47
See original GitHub issueConfiguration in launch.json:
{ "name": "Attach to API Module", "type": "node", "request": "attach", "port": 9230, "restart": true, "sourceMaps": true, "protocol": "inspector", "timeout": 60000, "skipFiles": ["<node_internals>/**/*.js"], "trace": true, }
Starting node:
After attaching Debugger it shows:
Then the console is stuck completely. No breakpoint stops. Disconnect doesn’t work. The node server itself just works fine. With earlier Versions ( <= 1.46 ) debugging was possible.
Log File vscode-debugadapter-1.json.gz
VS Code Version: 1.47
Additional context
Environment:
Running VS Code in WSL on Windows
Linux 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Okay, gotcha. I’ll add that to our COMMON_PROBLEMS.md – this had come up before but I couldn’t find the issue. Glad you got it working.
Thanks, I see you’re running nvm, so are you able to easily try on the latest 10.x, e.g.
10.22.1? If I recall there were a couple point releases in 10.x where things were broken, though I don’t reproduce any issues on Ubuntu running 10.16.0 myself.