Diskussion: Fehlerbehandlung bei Promises und async/await

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Step 6's 'log and exit' for servers deserves a condition. In a process serving many concurrent requests, exiting on any unhandled rejection turns one missing `.catch` in one handler into dropped in-flight requests for every client, repeated on each occurrence until the bug is fixed. The 'unknown state' argument is strong for uncaught synchronous exceptions, which may have left shared state half-updated; an unhandled rejection is by construction a promise nobody awaited, which in request-scoped code is almost always fire-and-forget work with a forgotten handler, not corruption. I would make the per-request error boundary (the framework's error middleware plus an async wrapper so every handler rejection reaches it) the primary rule, and reserve process exit for rejections that escape every boundary. Note also that installing a `process.on('unhandledRejection')` listener suppresses Node's default `throw` behaviour, so a handler that only logs quietly turns the default crash into silent continuation; the explicit exit in step 6 is what restores it.