skills.rest
i-bebsi
i-bebsiCOMMUNITY
Explore all skills by this author →
GitHub

node-inspect-debugger

Debug Node.js processes via the V8 inspector and Chrome DevTools Protocol.

Updated Jun 17, 2026
Search Tags:#vitest#debugging#nodejs#breakpoints#chrome devtools protocol#heap snapshot#v8 inspector
One-click install
npx skills add https://github.com/i-bebsi/hermes-agent --skill node-inspect-debugger-i-bebsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/i-bebsi/hermes-agent/tree/main/hermes-config/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/i-bebsi/hermes-agent --skill node-inspect-debugger-i-bebsi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface.

What problem does it solve? When console.log is not enough, this Skill gives you real breakpoints, step-through execution, call-stack inspection, and scope dumps for Node.js applications using the built-in V8 inspector and Chrome DevTools Protocol. ## Core Features & Use Cases - Interactive CLI Debugging: Use the built-in node inspect REPL to set breakpoints, step in/over/out, watch expressions, and evaluate code in the paused frame. - Programmatic CDP Automation: Script breakpoint management, scope capture, and expression evaluation with chrome-remote-interface for non-interactive debugging from an agent loop. - Profiling & Snapshots: Capture CPU profiles and heap snapshots from running processes for performance analysis in Chrome DevTools. - Use Case: A Vitest test fails with unclear state. Launch it with node --inspect-brk, attach the debugger, set a breakpoint at the suspect line, and inspect local and closure variables directly. ## 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 with breakpoints from the terminal?▼

Run node inspect script.js to launch the built-in debugger paused on the first line. Use sb('file.js', 42) to set breakpoints, c to continue, n to step over, and repl to evaluate expressions in the current scope.

How do I attach a debugger to an already running Node.js process?▼

Send SIGUSR1 to the process with kill -SIGUSR1 <pid> to enable the inspector, then attach with node inspect -p <pid> or via the WebSocket URL shown in the output. The process must be Node.js; child Python processes need a different debugger.

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

--inspect starts the inspector but lets the script run immediately, so you may miss early breakpoints. --inspect-brk pauses execution on the first line, giving you time to attach and set breakpoints before any code runs.

Why do my breakpoints hit the wrong lines in TypeScript files?▼

Breakpoints bind to the emitted JavaScript, not the .ts source. Either set breakpoints in the built dist/*.js files, or run Node with --enable-source-maps and use a CDP client that follows sourcemaps, since the node inspect CLI does not.

Can I capture a CPU profile or heap snapshot from a running Node process?▼

Yes, using chrome-remote-interface you can enable the Profiler or HeapProfiler domains over CDP. Start profiling, wait, then stop and write the result to a .cpuprofile or .heapsnapshot file for analysis in Chrome DevTools.

How do I debug Vitest tests without multiple workers interfering?▼

Run Vitest with --no-file-parallelism (or Jest with --runInBand) so only one worker exists, launched via node --inspect-brk ./node_modules/vitest/vitest.mjs. Then attach with node inspect and set breakpoints in the test or source files.

Related Skills

Explore More Software Engineering Skills→
drvossdrvoss
42

tdd-workflow

Enforce failing tests before implementation to drive Test-Driven Development workflows.

Community
Intermediate
akirschke15-cmdakirschke15-cmd

fix-loop

Automate test-driven debugging cycles to fix failing unit tests.

Community
Intermediate
fmflurryfmflurry
171

server-verbose-cocopenlog-debugging-techniques-2

Diagnose recurring server startup failures with hypothesis-driven debugging steps.

Community
Intermediate
carterwayneskhizeinecarterwayneskhizeine
19

python-debugpy

Debug Python programs with pdb breakpoints and debugpy remote DAP.

Community
Advanced