-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Just my code: introduce a magic path for core modules #16918
Comments
@roblourens any suggestion what 'magic path' (or better: 'magic segment') to use for core modules? |
We could use just We could also special case it with a new flag, |
Actually, that wouldn't work under what node2 does, which is to allow giving just the name of a file to skip, even if it's under some path. Would have to walk that back to use "*.js". Could allow |
@roblourens |
I will introduce a magic segment |
This will also be triggered if anyone evals a script and gives it a sourceURL of some name that isn't an absolute path. I don't think that would be very common in Node, but there's always some weird library, just FYI in case it ever comes up. Maybe we would have to hardcode the list of node script names as a workaround. |
Just my code: introduce a magic path for excluding/including core modules, e.g.:
In addition we should use the same magic path when showing core modules in the CALLSTACK view. This will fix the bogus path problem #16913.
The text was updated successfully, but these errors were encountered: