skills.rest
ZardLi1115
ZardLi1115COMMUNITY
Explore all skills by this author →
GitHub

node-inspect-debugger

Debug Node.js execution via V8 inspector with breakpoints and stepping.

4|Updated May 18, 2026
Search Tags:#debugging#cdp#nodejs#breakpoints#chrome-devtools#v8-inspector#ui-tui
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill node-inspect-debugger-zardli1115
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill node-inspect-debugger-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you diagnose failing Node.js behavior by letting you pause execution with real breakpoints and inspect locals, closures, and call stacks instead of relying only on console.log.

Core Features & Use Cases

  • Interactive debugging via node inspect: step in/over/out, set breakpoints by file/line or function name, and evaluate expressions in the paused frame.
  • Scriptable debugging via CDP: automate large breakpoint sets and state collection using chrome-remote-interface over the V8 inspector protocol.
  • Operate on running processes: attach to already-started Node targets (including dev servers and ZedClaw’s ui-tui) and debug without restarting when possible.

Use it when a unit test fails, the Ink/TUI UI misbehaves, a closure value is undefined, or async control flow “hangs” and you need a precise pause point and call path.

Quick Start

Start your script paused with node --inspect-brk path/to/script.js, then run node inspect -p <pid> and use sb('path/to/file.js', 42) followed by cont to hit your breakpoint.

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 Node.js execution with breakpoints instead of console.log?▼

Debug Node.js execution by attaching to the V8 inspector and controlling program flow with real breakpoints, stepping, and expression evaluation. This lets you pause execution and inspect locals, closures, and call stacks for precise diagnostics.

Can I attach a debugger to an already running Node.js process like a dev server?▼

Yes, you can attach to already-started Node targets, including dev servers and TUI applications, and debug without restarting when possible. This operates on running processes via the V8 inspector protocol.

Does Node.js debugging work with Ink and TUI runtime issues?▼

Yes, Node.js debugging applies to UI and TUI runtime issues built on Ink and tsx. You can attach to the running process to pause execution and inspect the exact state when the UI misbehaves.

How do I automate setting multiple breakpoints and collecting state in Node.js?▼

Use scriptable debugging via CDP with chrome-remote-interface over the V8 inspector protocol. This automates large breakpoint sets and state collection for automation-style investigations.

What do I need to use the Node.js V8 inspector for debugging?▼

You need an inspector-enabled Node target started with the --inspect or --inspect-brk flag. This prerequisite enables the V8 inspector protocol for both interactive node inspect CLI and CDP scripting sessions.

Related Skills

Explore More Software Engineering Skills→
markwang2658markwang2658
31

node-inspect-debugger

Debug Node.js processes via the Chrome DevTools Protocol.

Community
Intermediate
cabeznocabezno

node-inspect-debugger

Debugs Node.js programs via V8 inspect and Chrome DevTools Protocol.

Community
Advanced
anilcan-karaanilcan-kara

node-inspect-debugger

Attach to Node.js processes via Chrome DevTools Protocol for scripted debugging.

Community
Advanced
jaredcroxtonjaredcroxton

node-inspect-debugger

Attach to the V8 inspector to pause Node.js execution and inspect scopes.

Community
Intermediate