node-inspect-debugger

Inspect Node.js runtime state via breakpoints, stepping, and CDP.

Updated May 5, 2026

Search Tags:#typescript #debugging #cdp #nodejs #breakpoints #chrome-devtools #v8-inspector

Ready to run

npx skills add https://github.com/Z43L/zeus-agent --skill node-inspect-debugger-z43l

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/Z43L/zeus-agent/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/Z43L/zeus-agent --skill node-inspect-debugger-z43l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When Node.js behavior is unclear or tests fail, this Skill helps you pause execution at exact lines and inspect real runtime state so you can quickly pinpoint bugs that console logging can’t reveal.

Core Features & Use Cases

Breakpoint-driven inspection: Use Node’s V8 inspector to step in/over/out, view call stacks, and examine local and closure scopes while paused.
Interactive and scripted debugging: Drive debugging either via node inspect REPL or programmatically via CDP using chrome-remote-interface for repeatable automation.
Dev and UI debugging workflows: Inspect common issues in Ink/tsx-based UIs (including Vitest runs), attach to already-running Node processes, and debug non-interactive scenarios like heap snapshots or CPU profiles.

Quick Start

Use the node-inspect-debugger Skill to launch a paused session on your entry script and break at the suspicious line, then inspect variables in the paused frame.

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 application using breakpoints?▼

To debug Node.js with breakpoints, use the V8 inspector to pause execution at exact lines. You can step in, over, or out of code, inspect local and closure scopes, and evaluate expressions through the `node inspect` REPL or CDP.

When should I use Node V8 inspector instead of console logging?▼

Use the Node V8 inspector when behavior is unclear or tests fail and you need to inspect real runtime state. Breakpoints help quickly pinpoint bugs that console logging cannot reveal by showing the exact execution state at the moment of failure.

Can I attach a debugger to an already running Node process?▼

Yes, you can attach an inspector to already-running Node processes. This allows you to debug long-running dev servers or non-interactive scenarios like heap snapshots and CPU profiles without restarting the application.

Does Node V8 inspector work with Chrome DevTools and CDP?▼

Yes, the V8 inspector supports CDP via `chrome-remote-interface`. This allows you to drive debugging programmatically for repeatable automation, use Chrome DevTools, and inspect execution state interactively.

How do I debug UI rendering issues in Ink or tsx-based Node applications?▼

To debug UI rendering issues in Ink or tsx-based applications, use the V8 inspector to pause execution and inspect the call stack and scopes during Vitest runs. This helps identify state problems causing rendering failures.