-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: update V8 debugger doc to mention --inspect-brk #11495
Conversation
Node now supports the `--inspect-brk` flag, which does the same thing as `--inspect --debug-brk`. One thing that's nice about the new flag is that it uses "inspect" language -- this is a suggested update to the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's also good that you no longer have to use --inspect
and --debug-brk
, less typing is always nice.
@@ -197,8 +197,8 @@ V8 Inspector can be enabled by passing the `--inspect` flag when starting a | |||
Node.js application. It is also possible to supply a custom port with that flag, | |||
e.g. `--inspect=9222` will accept DevTools connections on port 9222. | |||
|
|||
To break on the first line of the application code, provide the `--debug-brk` | |||
flag in addition to `--inspect`. | |||
To break on the first line of the application code, pass the `--inspect-brk` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not going to stop or even slow this PR from landing over this incredibly minor thing I'm about to bring up, but I gotta ask: Why the provide
-> pass
change? (I think of pass
as something you do with arguments, not command-line flags, and so provide
feels more correct to me in this context. But I'm not sure if that's my own idiosyncrasy.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The paragraph above says "passing the --inspect
flag" so I followed its lead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for consistency, then!
Node now supports the `--inspect-brk` flag, which does the same thing as `--inspect --debug-brk`. One thing that's nice about the new flag is that it uses "inspect" language -- this is a suggested update to the docs. PR-URL: #11495 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Josh Gavant <josh.gavant@outlook.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Landed in ec4440a |
Node now supports the `--inspect-brk` flag, which does the same thing as `--inspect --debug-brk`. One thing that's nice about the new flag is that it uses "inspect" language -- this is a suggested update to the docs. PR-URL: nodejs#11495 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Josh Gavant <josh.gavant@outlook.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Node now supports the
--inspect-brk
flag, which does the same thingas
--inspect --debug-brk
. One thing that's nice about the new flag isthat it uses "inspect" language -- this is a suggested update to the
docs.
Checklist
Affected core subsystem(s)
doc