node-inspect-debugger

Attach the Node.js inspector and set breakpoints to debug runtime failures.

Updated May 26, 2026
One-click install
npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill node-inspect-debugger-ruiyangruiyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/ruiyangruiyi/hermes-agent/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill node-inspect-debugger-ruiyangruiyi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When Node.js behavior is unclear, this Skill helps you stop execution at the exact line and inspect the live scope state so you can identify why code fails or produces wrong results.

Core Features & Use Cases

  • Breakpoint-driven debugging: Step into/over/out, view call stacks, and walk paused frames to understand control flow precisely.
  • Scope and expression inspection: Dump local/closure variables and evaluate arbitrary expressions while the program is paused.
  • Interactive and scripted workflows: Use the built-in node inspect REPL for quick investigation or drive Chrome DevTools Protocol (CDP) for automation such as multi-breakpoint setup and reproducible debugging runs.

Quick Start

Use the Skill to debug a failing script by launching Node with an initial breakpoint and attaching the debugger CLI, then using breakpoints and step commands to inspect the paused state.

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 in the terminal?

To debug Node.js with terminal breakpoints, launch your script with an initial breakpoint flag and attach the `node inspect` REPL. This pauses execution at the exact line, allowing you to step through code and inspect live scope state to identify failures.

Can I inspect local variables and evaluate expressions while a Node.js process is paused?

Yes, while a Node.js process is paused at a breakpoint, you can dump local and closure variables or evaluate arbitrary expressions. This allows you to observe the runtime state and understand why code produces wrong results.

Does Node.js debugging support Chrome DevTools Protocol for automated breakpoint scripting?

Yes, Node.js debugging supports Chrome DevTools Protocol (CDP) scripting via `ws://` targets. You can automate multi-breakpoint setup, drive Runtime/Debugger inspection, and execute reproducible debugging runs for failing tests or dev-server hangs.

What is the best way to troubleshoot a hanging dev-server or failing unit test in Node.js?

The best way to troubleshoot Node.js hangs or test failures is attaching an inspector to the running process. Set breakpoints to observe control flow, walk paused call stacks, and inspect runtime state to pinpoint the exact failure source.

Are there connection limitations when using the V8 inspector for Node.js debugging?

Yes, the V8 inspector requires safe local-only connection guidance. You must attach the debugger to local processes or scripted CDP sessions securely to avoid exposing runtime inspection endpoints during debugging investigations.