Highlights: * Using a random port works (`node inspect --port=0 script.js`) * `takeHeapSnapshot()` creates valid snapshots again PR-URL: https://github.com/nodejs/node/pull/18354 Reviewed-By: Richard Lau <riclau@uk.ibm.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| lib | ||
| test/cli | ||
| tools/eslint-rules | ||
| .editorconfig | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| .travis.yml | ||
| appveyor.yml | ||
| CHANGELOG.md | ||
| cli.js | ||
| CONTRIBUTING.md | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
node-inspect
npm install --global node-inspect
For the old V8 debugger protocol, node has two options:
node --debug <file>: Startfilewith remote debugging enabled.node debug <file>: Start an interactive CLI debugger for<file>.
But for the Chrome inspector protocol,
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>