node-inspect-debugger

Debug Node.js applications via Chrome DevTools Protocol with breakpoints and stepping.

Updated Jun 4, 2026

Search Tags:#debugging #chrome devtools #cdp #nodejs #breakpoints

Ready to run

npx skills add https://github.com/kngender5/hermes --skill node-inspect-debugger-kngender5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/kngender5/hermes/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/kngender5/hermes --skill node-inspect-debugger-kngender5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of debugging Node.js applications by integrating Chrome DevTools Protocol, allowing developers to inspect and debug their applications programmatically from the terminal.

Core Features & Use Cases

Node.js Debugging: Offers two tools for debugging Node.js applications: node inspect and ndb/CDP via chrome-remote-interface.
Breakpoints and Stepping: Enables setting breakpoints, stepping through code, and inspecting call stacks and local/closure scopes.
Use Case: Ideal for debugging long-running processes, such as dev servers or TUI gateway, and for inspecting values in closures that are not accessible through console.log.

Quick Start

To debug a Node.js script, run: node inspect path/to/script.js

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 application using Chrome DevTools Protocol?▼

You can debug Node.js applications using Chrome DevTools Protocol by running the `node inspect` command or integrating `chrome-remote-interface` to programmatically connect and control the debugging session from your terminal.

Can I inspect closure variables in Node.js without using console.log?▼

Yes, you can inspect inaccessible closure variables by attaching Chrome DevTools Protocol to your Node.js process, which allows you to set breakpoints and directly evaluate local and closure scopes during execution.

How do I set breakpoints and step through a long-running Node.js dev server?▼

To set breakpoints and step through a long-running Node.js dev server, use `node inspect` or `ndb` via CDP to pause execution, inspect the call stack, and step through code programmatically without stopping the process.

Do I need chrome-remote-interface to debug Node.js from the terminal?▼

You need `chrome-remote-interface` if you want to programmatically interact with the Chrome DevTools Protocol for Node.js debugging, although the built-in `node inspect` command is also available for standard terminal debugging sessions.

What is the difference between node inspect and ndb for Node.js debugging?▼

`node inspect` provides built-in terminal debugging, while `ndb` integrates with Chrome DevTools Protocol via `chrome-remote-interface` to offer enhanced programmatic inspection of call stacks, closures, and breakpoints.

Why use Chrome DevTools Protocol instead of standard logging for Node.js debugging?▼

Using Chrome DevTools Protocol instead of standard logging allows you to inspect inaccessible closure values, set dynamic breakpoints, and step through long-running processes like dev servers without modifying code with temporary logs.