Node Inspect Debugger — Debug Node.js via --inspect + Chrome DevTools Protocol CLI
Node Inspect Debugger — Debug Node.js via --inspect + Chrome Devالأدوات Protocol CLI
Start with meaning, then move to detail.
This lesson explains Node Inspect Debugger — Debug Node.js via --inspect + Chrome DevTools Protocol CLI as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Node Inspect Debugger — Debug Node.js via --inspect + Chrome DevTools Protocol CLI without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Tool
- A structured action the agent can call to read or change something.
- Browser / CDP
- A layer for programmatic browser control and page or event inspection.
Debug Node.js via --inspect + Chrome DevTools Protocol CLI
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Overview
Read this after the foundation, then connect it to the previous step.
- 04When to Use
Read this after the foundation, then connect it to the previous step.
- 05Quick Reference: node inspect REPL
Read this after the foundation, then connect it to the previous step.
- 06Attaching to a Running Process
Read this after the foundation, then connect it to the previous step.
- 07Programmatic CDP (scripting from terminal)
Read this after the foundation, then connect it to the previous step.
- 08Debugging Hermes ui-tui
Read this after the foundation, then connect it to the previous step.
- 09Debugging a single Ink component under dev
Read this after the foundation, then connect it to the previous step.
- 10Debugging a running hermes --tui
Finish here to verify the result and special cases.
Copy only after you understand the effect.
node inspect path/to/script.js
# or with tsx
node --inspect-brk $(which tsx) path/to/script.ts# 1. Send SIGUSR1 to enable the inspector on an existing process
kill -SIGUSR1 <pid>
# Node prints: Debugger listening on ws://127.0.0.1:9229/<uuid>
# 2. Attach the debugger CLI
node inspect -p <pid>
# or by URL
node inspect ws://127.0.0.1:9229/<uuid>node --inspect script.js # listen on 127.0.0.1:9229, keep running
node --inspect-brk script.js # listen AND pause on first line
node --inspect=0.0.0.0:9230 script.js # custom host:portRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.