node-inspect-debugger

Debug a running Node.js process by starting it with the --inspect flag to expose the built-in inspector, then connect using the node inspect tool or a CDP client to attach and pause execution.

The Chrome DevTools Protocol (CDP) is used to programmatically automate Node.js debugging tasks, enabling multi-process scenarios, expression evaluation, and state inspection via terminal-based clients.

Yes, you can set real breakpoints, inspect variables, and walk the call stack by attaching the built-in inspector to a running Node.js process and connecting via the node inspect tool.

Evaluate expressions in a paused Node.js context by attaching to the process via the inspector, pausing execution at a breakpoint, and using CDP tooling or the node inspect interface to run expressions.

Yes, multi-process scenarios are supported by leveraging programmatic CDP tooling to automate debugging tasks across multiple running Node.js processes from the terminal.

No additional dependencies are required for basic terminal debugging beyond Node.js and its built-in node inspect tool, though optional CDP libraries are needed for programmatic automation.