skills.rest
swcstudiospace
swcstudiospaceOFFICIAL
Explore all skills by this author →
Website𝕏@govantarcticaGitHub

node-inspect-debugger

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

Updated Aug 19, 2026
Search Tags:#vitest#debugging#nodejs#breakpoints#chrome devtools protocol#heap snapshot#v8 inspector
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill node-inspect-debugger-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/node-inspect-debugger
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill node-inspect-debugger-swcstudiospace

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 from the terminal to set real breakpoints, step through code, walk call stacks, dump local and closure scopes, and evaluate arbitrary expressions in paused frames. ## Core Features & Use Cases - Interactive REPL debugging: Use the built-in node inspect CLI to set breakpoints, step in/over/out, watch expressions, and drop into a scoped REPL. - Attach to running processes: Enable the inspector on a live process with SIGUSR1 and attach by PID or WebSocket URL, including Ink-based TUI apps and Vitest test runs. - Programmatic CDP automation: Script breakpoints, scope dumps, CPU profiles, and heap snapshots with chrome-remote-interface for non-interactive debugging. - 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 closure variables that console.log could not reach. ## Quick Start Ask the agent to debug a failing Node 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 path/to/script.js to launch paused on the first line, then 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 the Node debugger to an already running 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 printed by Node. You can list targets at http://127.0.0.1:9229/json/list.

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

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

Can I debug TypeScript or tsx files with node inspect?▼

Yes, launch with node --inspect-brk --import tsx script.ts. 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 breakpoint never hit when debugging Node?▼

Common causes are attaching after execution finished (use --inspect-brk), wrong line numbers from TypeScript transpilation, or debugging a child process that did not inherit the inspector. Verify targets with curl http://127.0.0.1:9229/json/list.

How do I capture a CPU profile or heap snapshot from Node?▼

Use chrome-remote-interface to drive the Profiler and HeapProfiler domains over CDP. Start and stop Profiler for a .cpuprofile file, or call HeapProfiler.takeHeapSnapshot and write the chunks to a .heapsnapshot file for Chrome DevTools.

Related Skills

Explore More Software Engineering Skills→
alasdairncalasdairnc

e2e

Start the dev server, wait for readiness, and run Playwright tests with a single worker.

Community
Advanced
ebrahim-saniebrahim-sani

backtest-diagnose

Diagnose failed backtests by inspecting code, config, and artifacts.

Community
Advanced
nodesourcenodesource
6

ns-analyze-asset

Analyzes captured N|Solid CPU profiles, heap samples, and heap snapshots by asset ID.

Official
Advanced
carterwayneskhizeinecarterwayneskhizeine
19

python-debugpy

Debug Python programs with pdb breakpoints and debugpy remote DAP.

Community
Advanced