-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
module.register() will hang when debugging #2009
Comments
Weird, was yesterday able to reproduce it consistently, my suspicion is that it was a Node.js bug, which is probably fixed in recent Node.js - waiting for our customer to try out recent Node.js. |
I believe I've been encountering something similar for the past few days, where certain interactions between the VSCode debugger, Yarn and AWS-CDK causes a hang. I created a reproduction repo here, but thankfully found a workaround in the form of switching to the nightly version of the debugger extension. I haven't dug much more into it, but hopefully this helps someone. |
I'll close it for now since we are not able to reproduce anymore. We did a few changes around debugging (cwd, which might have been related) @Makeshift, if you still experience issues, I recommend filing a separate bug, so we don't mix. Thanks! |
Just for further reference, the issue in our case was: We were passing a
here:
Maybe we should validate that |
js-debug currently does no validation of the launch configuration passed to it. User-authored configurations will get warning diagnostics if they have something invalid in their launch.json based on the JSON schema, for API usages consumers just have to make sure they're giving valid data 🙂 |
Describe the bug
Debugging a JavaScript file which leverages
module.register
does end up in a infinite hang.To Reproduce
(following their example)
Steps to reproduce the behavior:
node test.js
Log File
N/A
VS Code Version: 1.90.0
Additional context
Looks like fixed in VSCode insiders - wasn't able to reproduce it there.
The text was updated successfully, but these errors were encountered: