# What changed in @remix-run/node-fetch-server

> 15 changes in @remix-run/node-fetch-server 0.11 to 1 from its official release notes, upgrade guides and advisories: 4 breaking, 3 new APIs and options. Each one cited. Sources checked 2026-10-24. HTML: https://unstale.sh/npm/@remix-run/node-fetch-server/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @remix-run/node-fetch-server 1

### Behavior and default changes

- The package reaches its first stable release. (1.0.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%401.0.0)

## @remix-run/node-fetch-server 0.14

### Breaking changes

- Request URLs use HTTP/2 :authority before Host; conflicting hosts receive a 400 response by default, with custom responses supported through onError. (0.14.2) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.2)
- Request handlers now receive native Request instances, fixing compatibility with standard APIs that rely on native Request internals. (0.14.1) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.1)

### New APIs and options

- Accepts request-only handlers separately from handlers that read client address information, allowing handlers such as router.fetch to be passed directly. (0.14.2) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.2)
- Adds trustProxy so trusted proxy headers can be used to construct request.url. (0.14.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.0)
- Adds trustProxy so trusted proxy headers can determine request.url and handler client address information. (0.14.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.0)

### Behavior and default changes

- Package modules are declared side-effect-free. (0.14.2) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.2)

### Fixes and other changes

- Avoids writing fallback error responses after streaming response headers are already committed. (0.14.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.0)
- Rejects request body reads when clients abort uploads. (0.14.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.14.0)

## @remix-run/node-fetch-server 0.13

### Breaking changes

- Responses are dropped after the client disconnects, and abort errors from handlers or response streams are no longer forwarded to onError or written to a closed socket. (0.13.3) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.13.3)

### Performance

- Request throughput now matches native node:http in the request-inspection benchmark while preserving Fetch API request handlers. (0.13.1) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.13.1)

### Fixes and other changes

- Unfinished streaming response bodies are canceled when the client disconnects before the response completes, so user-provided cancellation hooks run for aborted requests. (0.13.3) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.13.3)
- The first response stream chunk is written immediately, so streaming responses with a delayed second chunk flush initial data without unnecessary blocking. (0.13.2) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.13.2)
- Use the `:authority` header to set the URL of HTTP/2 requests. (0.13.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.13.0)

## @remix-run/node-fetch-server 0.11

### Breaking changes

- The CommonJS build was removed; the package is now ESM-only. CommonJS projects need to use dynamic import(). (0.11.0) — [release notes](https://github.com/remix-run/remix/releases/tag/node-fetch-server%400.11.0)