language

Node.js Errors

Node.js errors: ECONNREFUSED, ETIMEDOUT, EADDRINUSE, ERR_MODULE_NOT_FOUND, ERR_REQUIRE_ESM, EACCES, UnhandledPromiseRejection, MaxListenersExceededWarning, JavaScript heap out of memory.

Node errors split into system (libuv, prefixed E*), V8 (heap, stack), and Node-specific (ERR_*). Most production issues: ESM/CJS interop (ERR_REQUIRE_ESM), port conflicts (EADDRINUSE), unhandled promise rejections (now crash by default), and heap exhaustion on streaming JSON parsing. `--max-old-space-size` is a band-aid; find the leak.

Network (1)

EADDRINUSE

Address Already In Use

Your Node process tried to bind a TCP port (e.g., 3000) that another process is already listening on. The OS returns EADDRINUSE because two processes can't bind the same address+port. Often it's the previous instance of your own server that didn't shut down cleanly.

Configuration (1)

ERR_REQUIRE_ESM

Cannot Require ESM

Your CommonJS file used `require('some-package')` but the package is now ESM-only (its `package.json` has `"type": "module"` or `"exports"` only points to `.mjs`). Node's CJS loader can't synchronously load an ESM module.

Runtime (1)

heap_out_of_memory

Heap Out of Memory

V8's old-generation heap filled up and the garbage collector couldn't free enough space, so V8 aborts the process with a fatal allocation failure. Default heap is ~4GB on 64-bit; long-lived references (caches, listeners, closures, big arrays) prevent reclamation.

Official docs

https://nodejs.org/api/errors.html

Support

https://nodejs.org/en/get-involved/

Network (1)

Configuration (1)

Runtime (1)

Related services