OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2026-01-15 12:15:26 +00:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

cli: document --inspect port 0 behavior

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/53782
Reviewed-By: Kohei Ueno <kohei.ueno119@gmail.com>
This commit is contained in:
Aviv Keller
2024-07-18 10:28:44 -04:00
committed by GitHub
parent efe5b81df9
commit 3d019ce6af
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/api/cli.md
View File

@@ -1452,7 +1452,8 @@ or poisoning attack. Avoid using this option.
added: v6.3.0
-->
Activate inspector on `host:port`. Default is `127.0.0.1:9229`.
Activate inspector on `host:port`. Default is `127.0.0.1:9229`. If port `0` is
specified, a random available port will be used.
V8 inspector integration allows tools such as Chrome DevTools and IDEs to debug
and profile Node.js instances. The tools attach to Node.js instances via a
@@ -1486,7 +1487,8 @@ added: v7.6.0
-->
Activate inspector on `host:port` and break at start of user script.
Default `host:port` is `127.0.0.1:9229`.
Default `host:port` is `127.0.0.1:9229`. If port `0` is specified,
a random available port will be used.
See [V8 Inspector integration for Node.js][] for further explanation on Node.js debugger.
@@ -1499,7 +1501,8 @@ added: v7.6.0
Set the `host:port` to be used when the inspector is activated.
Useful when activating the inspector by sending the `SIGUSR1` signal.
Default host is `127.0.0.1`.
Default host is `127.0.0.1`. If port `0` is specified,
a random available port will be used.
See the [security warning][] below regarding the `host`
parameter usage.
@@ -1520,7 +1523,8 @@ added:
-->
Activate inspector on `host:port` and wait for debugger to be attached.
Default `host:port` is `127.0.0.1:9229`.
Default `host:port` is `127.0.0.1:9229`. If port `0` is specified,
a random available port will be used.
See [V8 Inspector integration for Node.js][] for further explanation on Node.js debugger.