Open cirosantilli opened 3 years ago
That's interesting, it looks like ends up calling debug
from the Command Line API instead of Debugger.setBreakpoint
, so there's not enough info from debug
to track it, even though the debugger will stop at that function.
Using debug
in Chrome Dev Tools also doesn't show a breakpoint in the Sources tab either.
I wonder if the tool could store a special type of breakpoint in knownBreakpoints
for listing it out, and then calling undebug
if you call clearBreakpoint
with a function name instead of a url/line.
It does look like it's currently matching the Chrome debugger behavior.
Thanks for the report! I think that would be a nice feature and I assume a PR adding this feature would likely be merged.
Still an issue in Node 22.4.1.
Hi, is this the upstream for what I describe below? :-)
main.js
Start debugging:
Leaves me at:
Now I set a breakpoint successfully:
but when I then run:
it just shows:
But
help
says: https://github.com/nodejs/node-inspect/blob/643179ef5e0452a52ceef2c5e7c8ca42ab00280f/lib/internal/inspect_repl.js#L57Tested on node v14.15.3.