node-inspect-debugger

Debug Node.js applications via the Chrome DevTools Protocol.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/lxh755818-bot/obsidian-vault --skill node-inspect-debugger-lxh755818-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/lxh755818-bot/obsidian-vault/tree/main/backup/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/lxh755818-bot/obsidian-vault --skill node-inspect-debugger-lxh755818-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a streamlined way to debug Node.js applications using the Chrome DevTools Protocol, making it easier to identify and fix issues in your code.

Core Features & Use Cases

  • Interactive Debugging: Use node inspect to step through your code, set breakpoints, and inspect variables.
  • Non-Interactive Debugging: Automate debugging tasks using scripts and the Chrome DevTools Protocol.
  • Use Case: When you encounter a bug in your Node.js application and need to inspect the state of your code at runtime.

Quick Start

Start debugging your Node.js application by running the following command: node inspect path/to/your/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 a Node.js application by running the `node inspect path/to/your/script.js` command to step through code execution, set breakpoints, and inspect variables via the Chrome DevTools Protocol.

What is the difference between interactive and non-interactive Node.js debugging?

Interactive debugging uses the `node inspect` command to manually step through code, while non-interactive debugging automates tasks using scripts and the Chrome DevTools Protocol without manual intervention.

Can I set breakpoints and inspect variables in Node.js without a browser?

Yes, you can set breakpoints and inspect variables using the `node inspect` command, which provides a debugging interface directly in your terminal leveraging the Chrome DevTools Protocol.

What do I need to start inspecting Node.js code execution at runtime?

You need a working Node.js environment and the Chrome DevTools Protocol. You can start inspecting code execution immediately by running `node inspect path/to/your/script.js`.

How do I automate debugging tasks for a Node.js script?

You can automate debugging tasks by utilizing non-interactive debugging scenarios with scripts that communicate via the Chrome DevTools Protocol to inspect and control your Node.js application.