[Solved] You want to debug a Node.js app that crashes immediately on start. You run node --inspect app.... What should you do to catch the crash at the start? | Node.js

Node.js - Debugging and Profiling

You want to debug a Node.js app that crashes immediately on start. You run node --inspect app.js and connect Chrome DevTools but can't find where it crashes. What should you do to catch the crash at the start?

AAdd <code>debugger;</code> inside app.js after the crash line

BRun with <code>node --inspect-brk app.js</code> to pause before code runs

CRun <code>node --inspect app.js</code> with extra logging

DUse <code>node debug app.js</code> instead

Step-by-Step Solution

Solution:

Step 1: Understand crash timing
If the app crashes immediately, you need to pause before any code runs to inspect it.
Step 2: Use correct flag to pause early
The --inspect-brk flag pauses execution on the first line, letting you catch early crashes.
Step 3: Evaluate other options
Adding debugger; after crash won't help if crash happens before it; extra logging may miss early crash; node debug is outdated.
Final Answer:
Run with node --inspect-brk app.js to pause before code runs -> Option B
Quick Check:
--inspect-brk pauses early to catch crashes [OK]

Quick Trick: Use --inspect-brk to pause before app starts [OK]

Common Mistakes:

Placing debugger after crash point
Relying only on logs for early crashes
Using deprecated debug command

Master "Debugging and Profiling" in Node.js

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More Node.js Quizzes

What should you do to catch the crash at the start?

Step 1: Understand crash timing

Step 2: Use correct flag to pause early

Step 3: Evaluate other options

Final Answer:

Quick Check:

Want More Practice?