node-inspect-debugger

Debug Node.js applications via the Chrome DevTools Protocol.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill node-inspect-debugger-lamseyahelias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/LamseyahElias/jarvis-cloud-v2/tree/main/hermes-agent/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill node-inspect-debugger-lamseyahelias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When console.log isn't enough, drive Node's built-in V8 inspector programmatically from the terminal. You get real breakpoints, step in/over/out, call-stack walking, local/closure scope dumps, and arbitrary expression evaluation in the paused frame.

Core Features & Use Cases

Two tools, pick one:

  • node inspect — built-in, zero install, CLI REPL. Best for quick poking.
  • ndb / CDP via chrome-remote-interface — scriptable from Node/Python; best when you want to automate many breakpoints, collect state across runs, or debug non-interactively from an agent loop. Prefer node inspect first. It's always available and the REPL is fast.

Quick Start

Launch your Node.js program with --inspect-brk to pause on start and attach a debugger.

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 applications with Chrome DevTools Protocol?

Debug Node.js applications with Chrome DevTools Protocol by leveraging the built-in inspector. You launch your program with --inspect-brk to pause execution, then attach a debugger to set breakpoints, walk the call stack, and inspect local scopes programmatically.

What is the difference between node inspect and chrome-remote-interface for Node.js debugging?

Node inspect is a built-in, zero-install CLI REPL best for quick interactive poking, whereas chrome-remote-interface enables scriptable, automated debugging sessions to set many breakpoints and collect state across non-interactive runs.

How do I set breakpoints and inspect scopes in a running Node.js process?

Set breakpoints and inspect scopes in a running Node.js process by attaching to it with --inspect or --inspect-brk. The built-in V8 inspector allows step-through execution, closure scope dumps, and arbitrary expression evaluation in the paused frame.

Can I automate Node.js debugging sessions programmatically without staying in a CLI REPL?

You can automate Node.js debugging sessions programmatically by accessing the Chrome DevTools Protocol via chrome-remote-interface. This allows you to script multiple breakpoints, collect state across runs, and debug non-interactively from an agent loop.

When should I use the built-in Node.js inspector instead of installing external debugging tools?

Use the built-in Node.js inspector when you need zero-install, fast CLI REPL access for quick poking. Prefer it first before external tools, as it is always available and provides immediate breakpoints, step-through debugging, and scope inspection.