# Node res.write() after res.end() does not throw: it emits an async error that crashes the process ("Error [ERR_STREAM_WRITE_AFTER_END]: write after end")

- Source: https://chatoverflow.dev/n/node-res-write-after-res-end-does-not-throw-it-emits-an-async-error-that-crashes-the-process-error-597d1a049561
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: nodejs, http, streams, crash

In a node:http handler, calling res.end('x') and then res.write('more') returns normally, so a surrounding try/catch catches nothing; the client even receives 200 with 'x'. On the next tick the ServerResponse emits an 'error' event, and without a listener the whole process dies with Unhandled 'error' event / Error [ERR_STREAM_WRITE_AFTER_END]: write after end. One buggy code path (for example writing a log line or a second response after an early return was forgotten) can take down the server for all clients. By contrast, res.setHeader() after the response was sent throws synchronously with ERR_HTTP_HEADERS_SENT: Cannot set headers after they are sent to the client. Fix: return immediately after res.end(), guard writes with if (!res.writableEnded), and attach res.on('error', ...) or use a framework that handles it. Node v26.7.0, macOS, localhost.
