node-inspect-debugger

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

5|2|Updated May 26, 2026
One-click install
npx skills add https://github.com/nyxoraAI/Nyxora --skill node-inspect-debugger-nyxoraai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/nyxoraAI/Nyxora/tree/main/packages/core/playbooks/software-development/node-inspect-debugger
Command: npx skills add https://github.com/nyxoraAI/Nyxora --skill node-inspect-debugger-nyxoraai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables developers to debug Node.js applications using the built-in V8 inspector, allowing for real breakpoints, step-by-step execution, and expression evaluation within the paused frame.

Core Features & Use Cases

  • Node.js Inspect: Offers real breakpoints and step-over/into/out capabilities for debugging.
  • CLI REPL: Provides a CLI-based REPL for quick debugging and poke-around.
  • Scriptable Automation: Allows automation of breakpoints and state collection for repetitive debugging tasks.
  • Use Case: Ideal for diagnosing issues in Node.js applications, especially during testing or when performance bottlenecks arise.

Quick Start

Run the node-inspect-debugger skill with the following command to start debugging your script:

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 breakpoints and step-by-step execution?

Debug Node.js applications by integrating with the V8 inspector and Chrome DevTools Protocol. This enables real breakpoints, step-over/into/out capabilities, and expression evaluation within the paused frame to diagnose issues.

Can I use Chrome DevTools Protocol to inspect Node.js test runs or performance bottlenecks?

Yes, Chrome DevTools Protocol inspects Node.js test runs and performance bottlenecks. It targets issues during development by connecting to the V8 inspector for real-time state collection and debugging.

What's the best way to automate repetitive debugging tasks in Node.js?

Automate repetitive Node.js debugging tasks using scriptable automation with the V8 inspector. This allows setting programmatic breakpoints and collecting state automatically during test runs or performance debugging.

Do I need chrome-remote-interface installed to debug Node.js via the V8 inspector?

Yes, chrome-remote-interface is required and must be installed and accessible. You also need the Node.js runtime installed to integrate with the V8 inspector and Chrome DevTools Protocol.

How do I start debugging my Node.js script from the CLI?

Start debugging your Node.js script by running the command 'node inspect path/to/script.js'. This launches the CLI-based REPL for quick poke-around debugging and step-by-step execution.

Why use a CLI-based REPL for Node.js debugging instead of a full GUI?

A CLI-based REPL for Node.js debugging provides quick poke-around capabilities without GUI overhead. It integrates with the V8 inspector for expression evaluation within paused frames, ideal for rapid diagnosis.