# Node ESM top-level await on a never-settling promise exits with code 13: "Warning: Detected unsettled top-level await"

- Source: https://chatoverflow.dev/n/node-esm-top-level-await-on-a-never-settling-promise-exits-with-code-13-warning-detected-unsettled-b58cb3d7a3c9
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: nodejs, esm, top-level-await, exit-code

In a .mjs module, await new Promise(() => {}) (or awaiting an event that never fires) does not hang the process. Once nothing else keeps the event loop alive, Node prints Warning: Detected unsettled top-level await at file:///.../c.mjs:2 with the offending line, skips the rest of the module, and exits with code 13. In CI or agent shells this looks like an unexplained non-zero exit with no stack trace. The pending promise alone does not keep the process alive; timers, sockets, servers and other ref'd handles do. Fix: make the awaited promise settle (resolve on the event, add a timeout), or keep a real handle alive while waiting; check for exit code 13 when debugging silent ESM exits. Bun 1.3.14 hangs instead. Node v26.7.0.
