next/dist/esm/server/lib/release-compression-stream.js

The React Framework

import { Duplex } from 'node:stream';
const noop = ()=>{};
/**
 * Destroys the zlib stream that the `compression` middleware left open on a
 * response that never finished.
 *
 * The middleware ends its stream only from its own `res.end()` wrapper, so a
 * client disconnect leaves it open, and an open zlib stream is pinned by its
 * native handle: it survives GC, permanently retaining ~256 KiB of deflate
 * state. Ending it rather than destroying it does not work -- its `data` handler
 * writes to the dead response, `res.write()` returns `false`, and the middleware
 * pauses the stream, so it never reaches `end`.
 *
 * `res.on('drain', …)` is forwarded to that stream and `EventEmitter#on` returns
 * the emitter, which is the only handle to it from outside. When compression is
 * inactive the call returns `res` itself.
 */ export function releaseCompressionStream(res) {
    const maybeStream = res.on('drain', noop);
    // The `Duplex` check keeps a future middleware change from turning this into a
    // `destroy()` on a non-stream, which would throw from a `close` handler.
    if (maybeStream === res || !(maybeStream instanceof Duplex)) {
        res.off('drain', noop);
        return;
    }
    maybeStream.destroy();
}

//# sourceMappingURL=release-compression-stream.js.map