skills.rest
vivekgoquest
vivekgoquestCOMMUNITY
Explore all skills by this author →
GitHub

node-inspect-debugger

Debug Node.js processes via --inspect and Chrome DevTools Protocol from the terminal.

Updated Aug 22, 2026
Search Tags:#debugging#cdp#nodejs#breakpoints#Chrome DevTools Protocol#v8 inspector#node inspect
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill node-inspect-debugger-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill node-inspect-debugger-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface.

What problem does it solve? When console.log is not enough, this Skill lets you drive Node's built-in V8 inspector programmatically from the terminal, giving you real breakpoints, step in/over/out, call-stack walking, scope dumps, and expression evaluation in paused frames. ## Core Features & Use Cases - Interactive REPL debugging: Use the built-in node inspect CLI to set breakpoints, step through code, watch expressions, and drop into a REPL with full access to locals and closures. - Programmatic CDP automation: Script breakpoint setup, scope capture, and expression evaluation with chrome-remote-interface for non-interactive or agent-driven debugging. - Attach to running processes: Enable the inspector on live Node processes with SIGUSR1, debug Ink-based TUI apps, run Vitest tests under the debugger, and capture CPU profiles or heap snapshots. - Use Case: A Vitest test fails in a TypeScript project. Launch it with node --inspect-brk, attach the debugger, set a breakpoint in the suspect file, and inspect the exact state at failure. ## Quick Start Ask the agent to debug a failing Node.js script by launching it with node --inspect-brk, attaching the inspector, and setting a breakpoint at the line you suspect.

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 from the command line?▼

Run node inspect path/to/script.js to launch paused on the first line with a debug REPL. Use commands like sb('file.js', 42) to set breakpoints, c to continue, n to step over, and repl to evaluate expressions in the current scope.

How to attach a debugger to a running Node.js process?▼

Send SIGUSR1 to the process with kill -SIGUSR1 <pid>, which makes Node print a WebSocket debugger URL. Then attach with node inspect -p <pid> or node inspect ws://127.0.0.1:9229/<uuid>.

What is the difference between --inspect and --inspect-brk?▼

--inspect starts the inspector but keeps the script running, so code may race past your breakpoints before you attach. --inspect-brk also pauses on the first line, letting you set breakpoints before any code executes.

Can I debug TypeScript files with node inspect?▼

Yes, run node --inspect-brk --import tsx script.ts to debug TypeScript via tsx. Note that breakpoints hit the emitted JavaScript lines, not the .ts source, unless you enable sourcemaps with a CDP client that follows them.

Why does my Node.js breakpoint never hit?▼

Common causes are using --inspect instead of --inspect-brk so execution finished before attaching, or setting breakpoints on TypeScript source lines that do not match the emitted JavaScript. Verify the target with curl http://127.0.0.1:9229/json/list.

When should I not use breakpoint debugging for Node.js?▼

Avoid it for problems console.log solves in under a minute, since breakpoint-driven debugging is heavier. Also use a Python debugger like debugpy for Python child processes, as the V8 inspector only covers Node portions.

Related Skills

Explore More Software Engineering Skills→
SatangThevalueSatangThevalue

node-inspect-debugger

Debug Node.js applications via inspector and Chrome DevTools Protocol.

Community
Advanced
spencerpaulyspencerpauly
672

parallel-test-fixing

Distribute failing test files across parallel subagents for Jest, Vitest, and Pytest.

Community
Advanced
rudolfolahrudolfolah
2

javascript-profiling

Profile Node.js CPU usage, heap allocation, garbage collection, and event-loop delay with built-in V8 tooling.

Community
Advanced
carterwayneskhizeinecarterwayneskhizeine
19

python-debugpy

Debug Python programs with pdb breakpoints and debugpy remote DAP.

Community
Advanced