Repository navigation
"breakpoints" command not listing breakpoints: "No breakpoints yet" #41790
Description
Hi, is this the upstream for what I describe below? :-)
main.js
#!/usr/bin/env node
function myfunc(i) {
return i + 1;
}
let i = 1;
i += 1;
console.log(myfunc(i));
Start debugging:
node inspect main.js
Leaves me at:
Break on start in main.js:7
5 }
6
> 7 let i = 1;
8 i += 1;
9 console.log(myfunc(i));
Now I set a breakpoint successfully:
sb('myfunc()')
but when I then run:
breakpoints
it just shows:
debug> breakpoints
No breakpoints yet
But help says: https://github.com/nodejs/node-inspect/blob/643179ef5e0452a52ceef2c5e7c8ca42ab00280f/lib/internal/inspect_repl.js#L57
Tested on node v14.15.3.
Activity
copperwall commentedon Dec 30, 2020
That's interesting, it looks like ends up calling
debugfrom the Command Line API instead ofDebugger.setBreakpoint, so there's not enough info fromdebugto track it, even though the debugger will stop at that function.Using
debugin 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
knownBreakpointsfor listing it out, and then callingundebugif you callclearBreakpointwith a function name instead of a url/line.It does look like it's currently matching the Chrome debugger behavior.
hybrist commentedon Jan 31, 2022
Thanks for the report! I think that would be a nice feature and I assume a PR adding this feature would likely be merged.
rotu commentedon Jul 10, 2024
Still an issue in Node 22.4.1.
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
rotu commentedon Jun 29, 2026
.
github-actions commentedon Sep 29, 2026
This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
rotu commentedon Sep 29, 2026
Has a human looked at this issue? @avivkeller, can we please disable the stale bot and improve issue triage instead.
avivkeller commentedon Sep 29, 2026
The stale bot allows us to keep active issues open, and inactive ones closed. This issue, as the stale bot has helpfully reported, seems to be inactive, but you are more than welcome to open a PR if you'd like to see the issue resolved.
avivkeller commentedon Sep 29, 2026
Node.js is a very high profile project, and it's maintained by a network of volunteers. We put a lot of effort into looking at issues, opening PRs, and making the project great for y'all. I'm not sure what you are asking us to improve?
rotu commentedon Sep 29, 2026
I'm thinking maybe have a bot try to reproduce the issue and close issues that fail to reproduce, are insufficiently detailed, are likely duplicates, or are unimportant. I'm sure there's more work to be done than anyone (especially volunteers!) can get around to, and it feels like staleness alone is not a great reason to throw away issue reports.
dualfroz commentedon Oct 14, 2026
picked up #53798 and finished it, PR is #66744 (rotu kept as co-author)