@react-router/serve
8.5.2 · 18 Nov 2026MIT1.8M / weekRepositorynpmAtom feed
Upgrading @react-router/serve From 7.18.6 to 8.5.2
10 releases in betweenevery note read
Reading releases, release notes and advisories…
- 2
- changes to make
- 0
- advisories fixed
- 1
- new
- 5
- fixes
Before you upgrade
Tick each one off as you go- Breaking8.0.0
- Breaking8.0.0
Release by release
8.5.2nothing new or fixed in the note
- Fixed
Avoid writing a blank line to stderr when the server shuts down successfully
- Fixed
- New
Support API-only builds in
react-router-serveby serving client documents and forwarding data and route discovery requests to the React Router runtime
- New
8.4.0nothing new or fixed in the note
- Fixed
Bump
@remix-run/node-fetch-serverdependency - Fixed
Serve
/.well-known/*files from the client build directory. Express 5's static middleware ignores every dot-segment path by default, so RFC 8615 well-known URIs — ACME challenges, Android'sassetlinks.json, Apple'sapple-app-site-association— fell through to the request handler and came back as app-rendered HTML instead of the static file. Other dotfiles remain hidden.
- Fixed
8.2.0 – 8.3.02 releases, nothing new or fixed in the notes
- Fixed
Use Node's built-in networking APIs to find an available port and remove the
get-portdependency
- Fixed
8.0.1nothing new or fixed in the note
31 internal lines (docs, tests, tooling) left out.
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.