1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: update links and names for DevTools Protocol

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/20111
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This commit is contained in:
Vse Mozhet Byt 2018-04-17 20:04:03 +03:00
parent e86b319e3f
commit c98eeb6b8d
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/api/cli.md
View File

@ -128,7 +128,7 @@ Activate inspector on host:port. Default is 127.0.0.1:9229.
V8 inspector integration allows tools such as Chrome DevTools and IDEs to debug 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 and profile Node.js instances. The tools attach to Node.js instances via a
tcp port and communicate using the [Chrome Debugging Protocol][]. tcp port and communicate using the [Chrome DevTools Protocol][].
### `--napi-modules` ### `--napi-modules`
@ -678,7 +678,7 @@ greater than `4` (its current default value). For more information, see the
[`Buffer`]: buffer.html#buffer_class_buffer [`Buffer`]: buffer.html#buffer_class_buffer
[`SlowBuffer`]: buffer.html#buffer_class_slowbuffer [`SlowBuffer`]: buffer.html#buffer_class_slowbuffer
[`process.setUncaughtExceptionCaptureCallback()`]: process.html#process_process_setuncaughtexceptioncapturecallback_fn [`process.setUncaughtExceptionCaptureCallback()`]: process.html#process_process_setuncaughtexceptioncapturecallback_fn
[Chrome Debugging Protocol]: https://chromedevtools.github.io/debugger-protocol-viewer [Chrome DevTools Protocol]: https://chromedevtools.github.io/devtools-protocol/
[REPL]: repl.html [REPL]: repl.html
[debugger]: debugger.html [debugger]: debugger.html
[emit_warning]: process.html#process_process_emitwarning_warning_type_code_ctor [emit_warning]: process.html#process_process_emitwarning_warning_type_code_ctor

4
doc/api/debugger.md
View File

@ -174,7 +174,7 @@ breakpoint)
V8 Inspector integration allows attaching Chrome DevTools to Node.js V8 Inspector integration allows attaching Chrome DevTools to Node.js
instances for debugging and profiling. It uses the instances for debugging and profiling. It uses the
[Chrome Debugging Protocol][]. [Chrome DevTools Protocol][].
V8 Inspector can be enabled by passing the `--inspect` flag when starting a 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, Node.js application. It is also possible to supply a custom port with that flag,
@ -194,5 +194,5 @@ To start debugging, open the following URL in Chrome:
at the end of the URL is generated on the fly, it varies in different at the end of the URL is generated on the fly, it varies in different
debugging sessions.) debugging sessions.)
[Chrome Debugging Protocol]: https://chromedevtools.github.io/debugger-protocol-viewer/ [Chrome DevTools Protocol]: https://chromedevtools.github.io/devtools-protocol/
[V8 Inspector]: #debugger_v8_inspector_integration_for_node_js [V8 Inspector]: #debugger_v8_inspector_integration_for_node_js

2
doc/node.1
View File

@ -114,7 +114,7 @@ Default is
.Sy 127.0.0.1:9229 . .Sy 127.0.0.1:9229 .
.Pp .Pp
V8 Inspector integration allows attaching Chrome DevTools and IDEs to Node.js instances for debugging and profiling. V8 Inspector integration allows attaching Chrome DevTools and IDEs to Node.js instances for debugging and profiling.
It uses the Chrome Debugging Protocol. It uses the Chrome DevTools Protocol.
. .
.It Fl -napi-modules .It Fl -napi-modules
Enable loading native modules compiled with the ABI-stable Node.js API (N-API) Enable loading native modules compiled with the ABI-stable Node.js API (N-API)