node-inspect-debugger

Name: node-inspect-debugger
Availability: InStock
Author: heximao

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

Updated May 11, 2026

Search Tags:#debugging #chrome devtools #node.js #cdp #node inspect

Ready to run

npx skills add https://github.com/heximao/agents --skill node-inspect-debugger-heximao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/heximao/agents/tree/main/skill-archive/docker-hermes/.archive/node-inspect-debugger
Command: npx skills add https://github.com/heximao/agents --skill node-inspect-debugger-heximao

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Debugging Node.js applications can be challenging without the right tools. This skill offers a comprehensive solution, allowing users to inspect and debug Node.js applications efficiently.

Core Features & Use Cases

Inspect Node.js Apps: Utilize Chrome DevTools Protocol (CDP) for debugging Node.js applications programmatically.
CLI Tools: Access built-in and scriptable CLI tools like node inspect and ndb.
Use Case: Debugging complex Node.js applications that require multiple breakpoints or state collection across runs.

Quick Start

Launch the Node.js application with inspection enabled using the command node --inspect script.js and attach a debugger CLI or scriptable interface.

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

Debug Node.js applications using Chrome DevTools Protocol by launching your script with `node --inspect script.js` and attaching a debugger CLI or scriptable interface to inspect complex logic.

What is the best way to inspect complex Node.js applications with multiple breakpoints?▼

Inspecting complex Node.js applications with multiple breakpoints is best handled by utilizing Chrome DevTools Protocol capabilities to collect state across runs via built-in CLI tools like `node inspect` and `ndb`.

Can I programmatically debug Node.js apps with chrome-remote-interface?▼

Yes, you can programmatically debug Node.js apps by utilizing the Chrome DevTools Protocol, which requires CDP support in the Node.js environment and optionally a driver script for automation.

Does Node.js debugging with CDP require any specific environment setup?▼

Node.js debugging with CDP requires CDP support in the Node.js environment. You must launch the application with inspection enabled using the `node --inspect script.js` command to attach a debugger.

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

Use Chrome DevTools Protocol instead of standard console logging when debugging complex logic, as it allows you to programmatically set multiple breakpoints and collect application state across runs.

When do I need a driver script for Node.js debugging?▼

You need a driver script for Node.js debugging when automating the inspection process programmatically via the Chrome DevTools Protocol, especially for applications with complex logic or multiple breakpoints.