node-inspect-debugger

Control the V8 inspector to debug Node.js runtime state with breakpoints and expression evaluation.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill node-inspect-debugger-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill node-inspect-debugger-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface.

What problem does it solve?

This Skill helps you debug failing Node.js programs when console output can’t reveal the real state at the moment the bug occurs.

Core Features & Use Cases

  • Breakpoint-driven debugging: Use Node’s built-in inspector to pause execution, step through code, and inspect locals/closures to pinpoint logic errors.
  • REPL-based investigation: Evaluate expressions in the paused frame via the node inspect REPL for rapid hypothesis testing.
  • Scriptable CDP automation: Use chrome-remote-interface to set breakpoints, walk scopes, and gather CPU/heap insights non-interactively for repeatable debugging.
  • Use Case: Debug an Ink + tsx UI component inside the Hermes ui-tui flow by pausing at a suspect render line, then inspecting props, refs, and input handlers before the UI updates.

Quick Start

Run your target with Node’s inspector (ideally using inspect-brk) and attach with node inspect for interactive stepping and expression evaluation.

Frequently Asked Questions about node-inspect-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Node.js script with breakpoints when console output isn't enough?

Debug Node.js scripts with breakpoints by starting the runtime with the --inspect or --inspect-brk flag, then attaching with node inspect to pause execution, step through code, and evaluate expressions in the paused frame.

Can I automate Chrome DevTools Protocol debugging for repeatable Node.js inspections?

Automate Chrome DevTools Protocol debugging using chrome-remote-interface to script non-interactive sessions, set breakpoints, enumerate scope properties, and collect heap snapshots or CPU profiles without manual intervention.

How do I debug a TypeScript TUI component pausing before the UI updates?

Debug TypeScript TUI components by attaching the Node inspector to pause execution at a suspect render line, allowing you to inspect props, refs, and input handlers before the UI updates.

What's the best way to inspect local variables and closures in a failing Node.js program?

Inspect local variables and closures in a failing Node.js program by using the node inspect REPL to pause at a breakpoint and evaluate expressions directly within the current execution frame.

Do I need chrome-remote-interface to use this Node.js V8 inspector debugging approach?

You only need chrome-remote-interface if you require scriptable CDP automation for repeatable, non-interactive debugging workflows; interactive breakpoint stepping uses Node's built-in inspector CLI instead.

What are the limitations of using the node inspect REPL for Node.js debugging?

The node inspect REPL is limited to interactive stepping and expression evaluation in paused frames, meaning it does not natively support automated heap snapshot collection or CPU profiling without CDP automation.