-
Notifications
You must be signed in to change notification settings - Fork 28.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
Can't debug builtin extensions #105859
Comments
So it doesn't load the sourcemaps at all unless they are in outfiles? I thought that is only used for pre-loading. |
We should load at runtime as well. I'll look at that. |
Oh, yea. By default, now for Node we set I think this is good behavior, actually. It makes things more deterministic -- if you set a breakpoint, in a file, we know that it will get bound and hit consistently, or it won't. Previously, poor configurations were 'hidden' by the runtime loading -- we'd hit the BP if we were able to load sourcemaps fast enough, but we might miss it sometimes. |
I think that does make sense. If I don't set outFiles, we do the best we can. If I set outFiles and it's wrong, we don't bind breakpoints in files that are missed by outFiles. I like things being deterministic. |
I was also having this issue when I upgraded to 1.49.0. My use case was debugging mocha tests. The fix for me was to add
As a side note, when I use "Add Configuration" --> "Node.js: Mocha Tests" the config added to launch.json includes: I have to remove the "-u" and the "tdd" for the debug to work. |
./extensions
The text was updated successfully, but these errors were encountered: