node-inspect-debugger

Capture a heap snapshot via Chrome DevTools Protocol automation to compare memory states before and after test runs. This identifies unexpected memory growth and objects retained between executions, revealing leaks that flaky Vitest tests often obscure.

Attach the native node inspect tool to a running Node.js process by its PID to set breakpoints and capture CPU profiles. This connects the debugger to live applications, enabling step-through execution and performance profiling without additional setup.

Yes, you can script Chrome DevTools Protocol automation to programmatically set breakpoints, capture heap snapshots, and generate CPU profiles. This enables repeatable debugging workflows to identify performance hot paths and memory leaks in Node.js applications.

Debug flaky Node.js test failures by pausing on test entry with the native inspector and inspecting async call stacks to find race conditions. Step-through debugging reveals timing issues that standard test runners cannot identify.

Yes, the native node inspect tool supports resolving hard-to-diagnose Node.js runtime issues including child process crashes. It enables inspector access and breakpoint management to step through code where the child process fails.

Use CPU profiles when standard logging cannot identify performance hot paths in Node.js applications. Generating a CPU profile via the inspector captures detailed runtime execution data, revealing bottlenecks that logs fail to expose.