ada-node-inspect-debugger

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-node-inspect-debugger-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-node-inspect-debugger
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-node-inspect-debugger
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-node-inspect-debugger-wubing7755

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 closure variable access for Node.js and TypeScript programs, all driven from the terminal without a GUI. ## Core Features & Use Cases - Interactive REPL Debugging: Launch node inspect to set breakpoints, step in/over/out, watch expressions, and evaluate arbitrary JavaScript in the paused frame. - Attach to Running Processes: Enable the inspector on a live process with SIGUSR1 and attach by PID or WebSocket URL, ideal for long-lived dev servers and TUI gateways. - Scriptable CDP Automation: Use chrome-remote-interface to programmatically set breakpoints, dump local and closure scopes, capture CPU profiles, and take heap snapshots. - Use Case: A Vitest test fails with unclear state. Run it under node --inspect-brk with --no-file-parallelism, attach the debugger, set a breakpoint at the suspect line, and inspect the actual variable values in the paused frame. ## Quick Start Ask the agent to run the failing Node script with --inspect-brk, attach node inspect, set a breakpoint at the suspect line, and print the local variables when it pauses.

Frequently Asked Questions about ada-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 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 from http://127.0.0.1:9229/json/list.

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 on the first line, giving you time to set breakpoints before any code executes.

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 without a GUI?

Yes. Use chrome-remote-interface to drive the Profiler and HeapProfiler domains over CDP, then write the .cpuprofile or .heapsnapshot output to disk and open it in Chrome DevTools for analysis.

When should I use console.log instead of the Node inspector?

Use console.log when it solves the problem in under a minute. Breakpoint-driven debugging is heavier and pays off when you need closure variables, call-stack walking, or state that logging cannot easily reach.