Node.js must be started with debugging enabled (e.g., --inspect flag) for VS Code to attach and stop at breakpoints.
Step 2: Consider other causes
Breakpoints on empty lines are ignored but usually not shown active. Minified code can cause mapping issues but breakpoints usually still stop. Missing launch.json prevents configuration but VS Code can attach manually.
Final Answer:
The Node.js process was started without the --inspect flag or equivalent debug option -> Option A
Quick Check:
Debugger needs --inspect flag to stop at breakpoints [OK]
Quick Trick:Start Node.js with --inspect to enable debugging [OK]
Common Mistakes:
Ignoring need for --inspect flag
Setting breakpoints on empty lines
Assuming launch.json absence blocks breakpoints
Master "Debugging and Profiling" in Node.js
9 interactive learning modes - each teaches the same concept differently