Here is a complete and beginner-friendly guide on Node.js Advanced Debugging, covering professional tools, techniques, and real-world debugging workflows.

🚀 Node.js Advanced Debugging

Debugging is a crucial part of backend development. Node.js provides multiple advanced techniques and tools to identify and fix bugs, performance issues, and memory leaks.

This guide covers:

✅ Debugging with Chrome DevTools
✅ VS Code Debugging
✅ Inspecting Variables & Call Stack
✅ Breakpoints (Manual & Conditional)
✅ Using console advanced tricks
✅ Performance profiling
✅ Memory leak debugging
✅ Using Node.js built-in debugger
✅ Debugging async code
✅ Logging best practices

🔍 1. Start Node.js with Debug Mode

Enable debugging:

Enable with break before start:

This opens the debugging interface in DevTools.

🧭 2. Debugging in Chrome DevTools

Open Chrome and go to:

Click:

👉 Open dedicated DevTools for Node

You get:

• Breakpoints

• Watch variables

• Scope inspection

• Call stack visualization

• Step-in / Step-out / Step-over

• Execution timeline

🧪 3. Debugging with VS Code (Recommended)

Create .vscode/launch.json

Features:

• Set breakpoints in code

• Hover variables

• Inspect call stack

• Pause on exceptions

• Debug async calls

• Restart on file save

🎯 4. Manual Breakpoints

You can force the debugger to pause using:

Example:

🎚️ 5. Conditional Breakpoints

Useful for breaking only when a condition is true:

In VS Code → Right-click breakpoint → Edit → Enter condition:

Or in DevTools.

🧩 6. Advanced console Debugging Techniques

Styled logs:

Table output:

Trace call stack:

Timing:

🧵 7. Debugging Asynchronous Code

Async stack traces:

Run Node with:

To debug promises:

🚦 8. Debugging Event Loop Lag

Check event loop delay:

⚡ 9. Performance Profiling (CPU Profiling)

Run CPU profiler:

Generate readable report:

Shows slow functions, blocking operations, etc.

🧠 10. Memory Leak Debugging

1. Start Node with heap snapshots:

2. In Chrome DevTools → Memory:

   • Take heap snapshots

   • Compare memory before & after operations

   • Find detached DOM nodes (if using SSR)

   • Find growing objects

3. Track heap usage:

🧽 11. Using Node’s Built-in Debugger (CLI)

Run:

Commands:

🛑 12. Debugging Crash Issues

Catch sync errors:

Catch async errors:

📝 13. Logging Best Practices

Use logging libraries instead of console.log():

Winston:

Example:

🌐 14. Debugging Production Apps

Use monitoring tools:

• PM2 Monitoring

• Sentry

• Datadog

• New Relic

• LogDNA

Example PM2 command:

🎁 Summary