mirror of https://github.com/lukechilds/node.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
30 lines
912 B
30 lines
912 B
8 years ago
|
# `node-inspect`
|
||
|
|
|
||
|
|
```bash
|
||
|
|
npm install --global node-inspect
|
||
|
|
```
|
||
|
|
|
||
|
|
For the old V8 debugger protocol,
|
||
|
|
node has two options:
|
||
|
|
|
||
|
|
1. `node --debug <file>`: Start `file` with remote debugging enabled.
|
||
|
|
2. `node debug <file>`: Start an interactive CLI debugger for `<file>`.
|
||
|
|
|
||
|
|
But for the Chrome inspector protol,
|
||
|
|
there's only one: `node --inspect <file>`.
|
||
|
|
|
||
|
|
This project tries to provide the missing second option
|
||
|
|
by re-implementing `node debug` against the new protocol.
|
||
|
|
|
||
|
|
```
|
||
|
|
Usage: node-inspect script.js
|
||
|
|
node-inspect <host>:<port>
|
||
|
|
```
|
||
|
|
|
||
|
|
#### References
|
||
|
|
|
||
|
|
* [Debugger Documentation](https://nodejs.org/api/debugger.html)
|
||
|
|
* [EPS: `node inspect` CLI debugger](https://github.com/nodejs/node-eps/pull/42)
|
||
|
|
* [Debugger Protocol Viewer](https://chromedevtools.github.io/debugger-protocol-viewer/)
|
||
|
|
* [Command Line API](https://developers.google.com/web/tools/chrome-devtools/debug/command-line/command-line-reference?hl=en)
|