NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #2839 most downloaded on npm
Cross Platform Smart Fetch Ponyfill
Latest stable
0.12.1
Last release 1 months ago
16 Oct 2026
Ships unpredictably
gaps range from 8 days to 10 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
796 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
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 →
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
[9527e8f]:
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
Updated dependency `@whatwg-node/node-fetch@^0.7.18` ↗︎ (from ^0.7.11, in dependencies)
f699a1b
Thanks @enisdenjo! - dependencies updates:
@whatwg-node/node-fetch@^0.7.18 ↗︎
(from ^0.7.11, in dependencies)Nothing published for this version
Updated dependencies [`31f021a`]:
#2093
31f021a
Thanks @ardatan! - Fixes the
TypeError: bodyInit.stream is not a function error thrown when
@whatwg-node/server is used with node:http2 and attempts the incoming
HTTP/2 request to parse with Request.json, Request.text,
Request.formData, or Request.blob methods.
Updated dependencies
[31f021a]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Updated dependency `@whatwg-node/node-fetch@^0.7.9` ↗︎ (from ^0.7.8, in dependencies)
#2082
b217e30
Thanks @ardatan! - dependencies updates:
@whatwg-node/node-fetch@^0.7.9 ↗︎
(from ^0.7.8, in dependencies)#2079
090b4b0
Thanks @ardatan! - Fix the bug when
set-cookies given is ignored in HeadersInit;
import { Headers } from "@whatwg-node/fetch";
const headers = new Headers([
["set-cookie", "a=b"],
["set-cookie", "c=d"],
]);
expect(headers.getSetCookie()).toEqual(["a=b", "c=d"]); // Previously it was empty
Updated dependencies
[090b4b0]:
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
Updated dependencies [`2785c80`]:
2785c80
Thanks @ardatan! - ReadableStream's
Symbol.asyncIterator now returns AsyncIterableIterator like before even if
it is ok to return AsyncIterator right now. It is safer to return
AsyncIterableIterator because it is a common mistake to use AsyncIterator
as AsyncIterable.2785c80]:
Nothing published for this version
Updated dependency `@whatwg-node/node-fetch@^0.7.5` ↗︎ (from ^0.7.1, in dependencies)
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
One column per quarter.