Tagged: async

Node.js process crashes with an unhandled promise rejection instead of just warning

Since Node.js 15, an unhandled promise rejection terminates the process by default instead of only printing a warning. Add a top-level `process.on('unhandledRejection', ...)` as a safety net, but the real fix is making sure every async call path actually has a `.catch()` or a surrounding try/catch.

Draft·

Nodejs

Error: The operation was aborted due to timeout (AbortSignal.timeout / TimeoutError)

AbortSignal.timeout(ms) fires an abort after the given duration, which surfaces wherever the signal was passed — most commonly into fetch() — as a TimeoutError (a DOMException). Catch it specifically and check `error.name === 'TimeoutError'` to distinguish it from other abort reasons or network failures.

Draft·