node-inspect-debugger

Node.js debugging from the terminal is automated by programmatically controlling the built-in inspector and Chrome DevTools Protocol to set breakpoints and inspect scope. This Skill drives paused sessions via a REPL and CDP automation for scriptable, reproducible debugging workflows.

Yes, attaching to running Node.js processes is supported by connecting via the inspector URL. This enables non-intrusive debugging of already active scripts, allowing you to inspect state and set breakpoints without restarting the process or interrupting execution flow.

Breakpoints are set by driving CDP-based tools and the built-in inspector through scriptable patterns. This approach automates Node.js debugging sessions by controlling the paused state, inspecting scope, and executing inspector commands programmatically rather than manually interacting with the debugger.

Automating reproducible debugging across runs and environments is achieved by launching scripts with --inspect or --inspect-brk and driving the session through CDP automation. This programmatic control over the built-in inspector ensures consistent breakpoint behavior and state introspection every time.

The inspector supports attaching to running processes and TBIs, including TypeScript or Deno-like contexts, via the inspector URL. This allows non-intrusive debugging across compatible runtimes that expose the standard Node.js inspector protocol for CDP automation and REPL control.

Programmatic CDP automation is ideal when you need reproducible, scriptable debugging across runs and environments rather than manual inspection. Use it to automate breakpoint setting, scope introspection, and paused session driving, replacing interactive workflows with repeatable Node.js debugging scripts.