node-inspect-debugger

To debug Node.js from the terminal, you attach to the live process using the built-in terminal debugger or Chrome DevTools Protocol. This allows you to set breakpoints, step through paused code, and inspect stack frames.

Yes, you can inspect closure scope values in a paused Node.js execution by attaching to the process via the inspector. This allows you to evaluate expressions and examine local variables within the current frame.

Debugging failing tests and child-process behavior in Node.js involves attaching the inspector to the runtime. You can set breakpoints in the test or child process path to step through execution and trace the root cause.

Yes, this debugging approach works with long-running services and TUI crashes. By attaching to the live Node.js process, you can pause execution at breakpoints to investigate the paused-frame state and stack traces.

The best way to capture CPU profiles and heap snapshots in Node.js is by using the Chrome DevTools Protocol. This allows you to attach to the live process and run optional CPU or heap profiling to check runtime performance.

You should use the Chrome DevTools Protocol instead of the terminal debugger when you need scripted, repeatable debugging sessions. The terminal debugger is better suited for quick, interactive investigations of stack frames.