node-inspect-debugger

npx skills add HezaoHezao/poirot --skill node-inspect-debugger --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Node.js Inspect Debugger ## Overview When `console.log` isn't enough, drive Node's built-in V8 inspector programmatically from the terminal. Real breakpoints, step in/over/out, call-stack walking, scope dumps, and arbitrary expression evaluation. **Prefer `node inspect` first.** It's always available and the REPL is fast. ## When to Use - A Node test fails and you need to see intermediate state - A Node process crashes or behaves wrong and you want to inspect state - You need to inspect a value in a closure that `console.log` can't reach - Perf: attach to a running process to capture a CPU profile or heap snapshot **Don't use for:** things `console.log` solves in under a minute. ## Quick Reference: `node inspect` REPL Launch paused on first line: ```bash node inspect path/to/script.js # or with tsx node --inspect-brk $(which tsx) path/to/script.ts ``` The `debug>` prompt accepts: | Command | Action | |---------|--------| | `c` | continue | | `n` | next line (step over) | | `s` | step into | | `o` | step out | | `sb('file.js', line)` | set breakpoint | | `cb('file.js', line)` | clear breakpoint | | `watch('expr')` | watch expression | | `exec('expr')` | evaluate in paused frame |

node inspect path/to/script.js
or with tsx
node --inspect-brk $(which tsx) path/to/script.ts
Install
npm install chrome-remote-interface
Launch node with inspect
node --inspect-brk=9229 path/to/script.js &
Attach via script
node -e "
const CDP = require('chrome-remote-interface');