@remix-run/node-fetch-server
1.0.1 · 19 Nov 2026MIT5.4M / weekRepositoryHomepagenpmAtom feed
15 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 1.x · latest line
1.0.1
19 Nov 2026createRequest()andcreateRequestListener()now validate the request host for every handler, including handlers that take no arguments. The effective host, whether it comes from thehostoption, a trustedForwardedorX-Forwarded-Hostheader, HTTP/2:authority, orHost, must be a hostname or bracketed IPv6 address with an optional port. Values with a path, query, fragment, userinfo, whitespace, or control characters, such asexample.com/../adminoruser@example.com, makecreateRequest()throw.createRequestListener()passes the error toonErrorand responds with400 Bad RequestunlessonErrorreturns a response. An invalid trustedX-Forwarded-Hostis rejected instead of falling back toHost.
1.0.0
1 Oct 2026- Breaking
First stable release.
- 0.14.x
0.14.2
28 Sep 2026Use HTTP/2
:authoritybeforeHostwhen constructing request URLs. Requests whoseHostand:authorityidentify different hosts now receive a 400 response by default fromcreateRequestListener(), with custom responses supported throughonError. Equivalent hostnames and default ports remain accepted.createRequestListener()now accepts request-only handlers separately from handlers that read client address information, so handlers such asrouter.fetchcan be passed directly.Declare package modules as side-effect-free.
0.14.1
14 Aug 2026Request handlers now receive native
Requestinstances instead of lazy request objects that emulated native requests. This fixes compatibility with standard APIs likenew Request(request, init)that rely on nativeRequestinternals.
0.14.0
1 Jul 2026Added a
trustProxyoption tocreateRequestListener()andcreateRequest()so apps behind trusted reverse proxies can constructrequest.urlfromForwarded,X-Forwarded-Host, andX-Forwarded-Protoheaders.createRequestListener()also uses trustedForwardedandX-Forwarded-Forvalues for handler client address information (see #10874).
- 0.13.x
0.13.3
20 May 2026Cancel unfinished streaming response bodies when the client connection closes before the response completes so user-provided
ReadableStream.cancel()hooks run for aborted requests (see #11432).Drop handler responses when the client has already disconnected, and do not forward request abort errors from handlers or response streams to
onErroror write them to a closed socket (see #11431).
0.13.2
20 May 2026Start writing the first response stream chunk immediately instead of waiting for another chunk. Streaming responses with a delayed second chunk now flush their initial data without unnecessary blocking.
0.13.1
30 Apr 2026Improve request throughput so
node-fetch-serveris now on par with nativenode:httpperformance in the request-inspection benchmark, while preserving Fetch API request handlers. The main optimizations lazily materializeRequestandHeadersobjects, specialize handlers by declared arity, avoid unnecessary client/request work on hot paths, and send single-chunk response bodies with less Web stream overhead. See thenode-fetch-serverbenchmarks for current results.
0.13.0
18 Dec 2025Use the
:authorityheader to set the URL of http/2 requests.
- 0.12.x
0.12.0
4 Nov 2025Use
tscdirectly instead ofesbuildto build the package. This means modules in thedistdirectory now mirror the layout of modules in thesrcdirectory.
- 0.11.x
0.11.0
22 Oct 2025- Breaking
Removed CommonJS build. This package is now ESM-only. If you need to use this package in a CommonJS project, you will need to use dynamic
import().
- 0.10.x
0.10.0
4 Oct 2025Fire
closeandfinishlisteners only once
- 0.9.x
0.9.0
16 Sep 2025Support
statusTextin HTTP/1 responses
- 0.8.x
0.8.0
24 Jul 2025Renamed package from
@mjackson/node-fetch-serverto@remix-run/node-fetch-serverHandle backpressure correctly in response streaming
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.