node-inspect-debugger

Set Node.js breakpoints by attaching to the V8 inspector to pause execution, set breakpoints, and inspect scope values and call stacks. Use the node inspect REPL with sb('path/to/file.js', lineNumber) to set a breakpoint, then continue execution and use repl to inspect variables when paused.

Yes, you can evaluate arbitrary expressions in the paused frame to dump local and closure variables. This lets you inspect component props, hooks-local values, and rendering conditions directly when execution is paused at a breakpoint.

Yes, you can drive the V8 inspector via CDP for repeatable automation and batch data collection. This requires programmatic CDP access using chrome-remote-interface to automate scripted debugging workflows instead of using the interactive node inspect REPL.

Set a breakpoint at the suspect render path or failing test execution, pause execution, and inspect component props and hooks-local values. Use step in/over/out, backtrace, and source listing to pinpoint exactly where control flow goes wrong in the UI or test.

Yes, you need to start your script with node --inspect-brk or use the node inspect command to attach to the V8 inspector. This pauses execution at the start so you can set breakpoints via sb() before the code runs.