NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #2643 most downloaded on npm
Fetch API implementation for Node
Last release 4 days ago
30 Sep 2026
Ships unpredictably
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
1378 releases · first in 2022
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
It is actually a bug in compression package; expressjs/compression#46 But since it is a common mistake, we prefer to workaround this on our end.
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression npm package do not implement response.write(data, callback)
signature, but whatwg-node/server waits for it to finish the response stream.
Then it causes the response stream hangs when the compression package takes
the stream over when the response data is larger than its threshold.
It is actually a bug in compression package;
expressjs/compression#46
But since it is a common mistake, we prefer to workaround this on our end.
Now after calling response.write, it no longer uses callback but first it
checks the result;
if it is true, it means stream is drained and we can call response.end
immediately. else if it is false, it means the stream is not drained yet, so
we can wait for the drain event to call response.end.
Updated dependencies
[d86b4f3]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added dependency `@fastify/busboy@^3.1.1` ↗︎ (to dependencies)
#2305
380984a
Thanks @enisdenjo! - dependencies updates:
@fastify/busboy@^3.1.1 ↗︎
(to dependencies)busboy@^1.6.0 ↗︎ (from
dependencies)#2305
380984a
Thanks @enisdenjo! - Abort parsing form data
if the request is aborted
#2305
380984a
Thanks @enisdenjo! - Handle parsing form data
when supplied Content-Length header value is smaller than the actual data
Updated dependencies
[6bf6aa0]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →