Let’s Debug a Node.js Application

Summary

Node.js applications can be difficult to debug because asynchronous workflows complicate stack traces, while crashes may require core-dump analysis through complex command-line tools. The article presents a layered toolkit: production-oriented logging with Pino or Winston, interactive inspection through Node Inspect and Chrome DevTools, IDE integrations, and the standalone ndb debugger. Running node --inspect-brk launches an application for inspection at chrome://inspect, where breakpoints, stepping, call stacks, heap snapshots, and memory profiling are available; ndb additionally supports edit-in-place changes. For catastrophic crashes, llnode maps JavaScript frames and objects to C/C++ representations from a core dump generated with process.abort, while debug filters namespaced logs and trace and clarify improve asynchronous traces and remove Node.js internals, respectively, for local debugging.

Takeaways

1. 1

   The debug module assigns namespaces to log messages and uses the DEBUG environment variable to selectively display messages, such as express:router output.

2. 2

   trace adds detail about asynchronous methods to stack traces, while clarify removes Node.js-internal frames; neither module is recommended for production use.

3. 3

   llnode inspects JavaScript stack frames and objects after a crash by mapping them to C/C++-side objects, using a core dump generated with process.abort.