node-inspect-debugger

Debug Node.js runtime failures via V8 inspector breakpoints and CDP.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill node-inspect-debugger-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/devMoez/titan/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/devMoez/titan --skill node-inspect-debugger-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of not understanding why a Node.js program misbehaves when console logs are insufficient, by letting you pause execution and inspect live state at the exact line you care about.

Core Features & Use Cases

  • Breakpoints and stepping: Use Node’s V8 inspector to continue, step into/over/out, pause, and walk the call stack to locate the true failing path.
  • Scope inspection and expression evaluation: Inspect locals/closure variables and evaluate arbitrary JavaScript expressions while paused to understand runtime data.
  • Automated CDP debugging: Drive Chrome DevTools Protocol from a terminal script to set many breakpoints, capture state across pauses, and reproduce issues non-interactively.
  • Use cases: Debug failing Node scripts, trace issues in TypeScript/tsx projects, inspect Ink-based ui-tui behavior, and diagnose runtime problems before they surface in logs.

Quick Start

Use the node-inspect-debugger skill to debug a failing Node script by starting it with --inspect-brk and then using node inspect to set a breakpoint at the suspicious source line and continue execution until it pauses there.

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 instead of console logs?

Debug a Node.js script by starting it with --inspect-brk and using node inspect to set breakpoints, pause execution, and inspect live state at the exact failing line.

Can I evaluate expressions and inspect scope variables while paused in the V8 inspector?

Yes, the V8 inspector lets you inspect locals and closure variables, evaluate arbitrary JavaScript expressions while paused, and walk the call stack to locate the failing path.

Does Node.js debugging work with TypeScript and tsx workflows?

Node.js debugging supports TypeScript and tsx workflows by pausing execution via the V8 inspector to trace runtime issues before they surface in logs.

What is the best way to set multiple breakpoints non-interactively in Node.js?

Automated CDP debugging drives the Chrome DevTools Protocol from a terminal script to set many breakpoints, capture state across pauses, and reproduce issues non-interactively.

How do I step through a Node.js call stack to find the true failing path?

Use Node's V8 inspector to continue, step into, step over, step out, and pause execution to walk the call stack and find the true failing path.

When should I use the V8 inspector instead of adding more console logs?

Use the V8 inspector when console logs are insufficient and you need to pause execution to inspect live runtime data and understand why a Node.js program misbehaves.