NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2643 most downloaded on npm
Fetch API implementation for Node
Latest stable
0.9.4
Last release 11 days ago
10 Nov 2026
Release timing varies
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
1419 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
Repeated body accesses no longer allocate a fresh Proxy (and method binds) on every get when the generated stream identity is stable.
#3793
f778c82
Thanks @ardatan! - Cache the body Proxy while
the underlying Node readable is unchanged.
Repeated body accesses no longer allocate a fresh Proxy (and method binds)
on every get when the generated stream identity is stable.
Updated dependencies
[f778c82]:
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
@whatwg-node/node-fetch@0.9.3
@whatwg-node/node-fetch@0.9.3
#3738
10f0d28
Thanks @wleeaf! - Skip a leading UTF-8 byte order
mark in text() and json(), as UTF-8 decode does. A JSON body that starts
with a byte order mark made json() throw a SyntaxError.
#3746
2a37f7d
Thanks @ardatan! - Sort header names when
iterating, per Fetch sort-and-combine. Repeated names stay combined, and
set-cookie values stay separate in sorted name order.
84f7f2e
Thanks @wleeaf! - Keep every value of a header
name that is repeated in a sequence passed to Headers.
Changing, adding or deleting another header kept only the last value of the
name, set() replaced only the first value, and iteration returned the pairs
as given instead of one combined entry with a lowercase name. A server
response built with [["link", "<a>"], ["link", "<b>"]] was sent with
link: <b> only.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
@whatwg-node/node-fetch@0.9.2
@whatwg-node/node-fetch@0.9.2
#3694
f927bd2
Thanks @dependabot! - dependencies
updates:
@fastify/busboy@^3.2.3 ↗︎
(from ^3.1.1, in dependencies)#3715
06e7013
Thanks @ardatan! - Fulfill pending
reader.read() as { done: true } when cancel(reason) runs, matching the
WHATWG ReadableStream cancel algorithm (and native undici).
Previously cancel() called readable.destroy() without ending the stream
first, so an in-flight read() rejected with ERR_STREAM_PREMATURE_CLOSE /
Premature close instead of settling as done. The cancel reason still
reaches underlyingSource.cancel(reason).
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
@whatwg-node/node-fetch@0.9.1
@whatwg-node/node-fetch@0.9.1
#3642
ed29dc2
Thanks @ardatan! - Follow the Fetch standard
when the Node HTTP transport follows redirects.
fetchNodeHttp recursed on every 3xx Location while redirect was
'follow' (the default) and never counted hops. A response that always
redirects could keep one fetch call issuing requests until the process ran
out of memory. Following now stops after 20 redirects. The promise rejects
with TypeError: Fetch failed: Maximum number of redirects (20) reached and
code TooManyRedirects. A chain of 20 redirects that then returns a normal
response still completes.
That path also reused the previous request's Headers object for the next
hop. A cross-origin Location therefore received Authorization,
Proxy-Authorization, Cookie, Cookie2, and an explicit Host. Those
headers are removed when the origin changes. The scheme is part of the origin,
so an https to http redirect drops them too. Same-origin redirects still
send them. Removal happens on a new header list, so the caller's own Headers
object is left unchanged.
301 and 302 responses to POST, and 303 responses to any method other
than GET or HEAD, are resent as GET with no body. The request-body
headers go with the body: Content-Encoding, Content-Language,
Content-Location, Content-Type, and Content-Length. 307 and 308 keep
the method and body when that body can be sent again. A one-shot stream
cannot, and that redirect rejects.
A cross-origin redirect whose URL includes a username or password is rejected
with TypeError when the request mode is cors. Following it would send
those URL credentials to the new origin as Authorization.
A resent FormData body is encoded again with a new multipart boundary of the
same length, so its Content-Length stays valid. Content-Type is replaced
because that header names the boundary.
redirect: 'error' rejects with a TypeError. A redirect whose target scheme
is not http or https also rejects with a TypeError. redirect: 'manual'
still returns the redirect response.
Response.redirect() serializes an absolute URL into the Location header
and throws TypeError when that URL cannot be parsed. A relative URL is
stored as given, so Response.redirect('/') sets Location to /. The
status must be 301, 302, 303, 307, or 308; any other status throws
RangeError. The response status text is empty.
@whatwg-node/fetch uses this transport on Node, so the same limits apply
there.
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
One column per quarter.