Have you ever...

1. Spent three hours on a bug that turned out to be an unawaited promise?
2. Watched your app crash in production with not a single useful stack trace?
3. Restarted a server with your fingers crossed, not really knowing what just happened?
4. Stared at a memory profile wondering what those 200 MB are doing there?

You're not alone. On average, developers spend 30 to 50 % of their time debugging. It's one of the highest-leverage skills you can build — and paradoxically, one of the least taught.

THIS BOOK IS HERE TO FIX THAT.

─

WHAT YOU'LL GET

1. A repeatable method — R.A.P.I.D.E. Six steps to tackle any bug, no matter how weird. No more "it works now" without knowing why.
2. Real runtime intuition. Event loop, microtasks, generational GC, libuv thread pool. Once you know what Node actually does under the hood, bugs become predictable.
3. The complete toolbox. --inspect, Chrome DevTools, VS Code, clinic.js, 0x, pino, OpenTelemetry, heap snapshots, --prof. Which tool for which symptom, and when.
4. Logging that saves you at 3 AM. pino + AsyncLocalStorage, copy-paste-ready. reqId auto-propagated. Log levels that actually mean something. Secrets redacted.
5. Async errors demystified. Unawaited promises, async forEach, try/catch that doesn't catch, unhandledRejection. Every pitfall, every fix.
6. Performance, measured. Detect a CPU block. Hunt a memory leak with two heap snapshots. Monitor event loop lag.
7. Production without panic. Hot-attach the inspector. Capture a heap snapshot without restarting. Which indicators to watch. How to stop the bleeding during an incident.

─

THIS BOOK IS FOR YOU IF...

✓ You write Node.js daily (REST APIs, GraphQL, CLIs, workers, microservices, scripts) and you're tired of guessing.

✓ You know how to build, but struggle to fix.

✓ You want a method, not just another list of tools.

✓ You'd rather have copy-paste-ready code than diluted theory.

THIS BOOK IS NOT FOR YOU IF...

✗ You're new to JavaScript (go learn the basics first).

✗ You're looking for a "how to build an API" tutorial.

✗ You want frontend (React, Vue, Angular).

─

TABLE OF CONTENTS

Preface

1. Introduction to debugging Node.js

2. Understanding the Node.js runtime

3. Native debugging tools

4. Debugging with VS Code and Chrome DevTools

5. Effective logging

6. Async errors

7. Performance: CPU, memory, and leaks

8. Debugging REST and GraphQL APIs

9. Workers, queues, and microservices

10. Debugging in production

11. Checklist and toolbox

Appendices

A. 15 commands worth memorizing

B. Quick glossary

C. Further reading (books, docs, talks)

Conclusion

─

ABOUT THE AUTHOR

https://github.com/papac

Franck DAKIA has been shipping Node.js for years — APIs, CLIs, microservices, ETL scripts. Like everyone else, he's spent nights debugging. This book is what he wishes he had read at the start.

────────────────────────────────────────────────

No fluff. No "intro to JavaScript" to pad the page count. Just the tools, methods, and patterns that make the difference between "I pushed a fix that should work" and "I know exactly why the bug was happening."

Hit Buy and stop restarting your server with your fingers crossed.