-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Node.js debugging async emitHookFactory #49402
Comments
(Experimental duplicate detection) |
You can! Just add
To your launch config and you will skip through those files, same as "blackboxing" using chrome devtools. |
Would you consider making this the default with a launch configuration of type node ? |
Possibly. Need to do some thinking around this and also microsoft/vscode-chrome-debug-core#245 |
Issue Type: Feature Request
While debugging node.js with async function, I often end up in the function emitHookFactory from the node internal scripts.
The debugging experience would be better if that function was skipped as it has no value to the user.
VS Code version: Code 1.22.2 (3aeede7, 2018-04-12T16:38:45.278Z)
OS version: Windows_NT x64 10.0.17665
The text was updated successfully, but these errors were encountered: