@react-router/dev
8.5.2 · 18 Nov 2026MIT4.5M / weekRepositoryHomepagenpmAtom feed
64 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 8.x · latest line
8.5.2
18 Nov 2026Cache client route chunk analysis using normalized route paths and disable dependency optimization in the child compiler, including explicitly included dependencies
Serialize concurrent type generation to prevent filesystem races between
react-router devandreact-router typegenPass route component props to exports declared with export specifiers
Patch Changes
Cache client route chunk analysis using normalized route paths and disable dependency optimization in the child compiler, including explicitly included dependencies
Serialize concurrent type generation to prevent filesystem races between
react-router devandreact-router typegenReport a timeout with cleanup instructions if the typegen lock cannot be acquired within 30 seconds
Pass route component props to exports declared with export specifiers
Pass props such as
loaderDataandparamstodefault,ErrorBoundary, andHydrateFallbackexportsSupport re-exports such as
export { default } from "./component"and local aliases such asexport { Page as default }
Improve handling of prerendered redirect destinations in Framework Mode and unstable RSC Framework Mode
Declare an empty source map for the placeholder chunk of a route export that can't be split, so Rollup no longer warns that
react-router:split-route-modulesdropped the source mapPreserve RSC client middleware when route components update via HMR
Fix RSC Framework Mode builds failing with "Vite RSC assets manifest not found" when using
@vitejs/plugin-rsc0.5.36 or laterPreserve client version checks when the client build uses
write: false
Avoid adding
isbotto dependencies whenssr: false
8.5.1
27 Oct 2026Use resolved Vite environment output directories when reading and writing build artifacts
Run prerendering after other Vite plugins finish their application build hooks
Patch Changes
Use resolved Vite environment output directories when reading and writing build artifacts
Finalize server-bundle manifest paths after asynchronous Vite configuration hooks complete
Preserve output-directory overrides applied when creating a Vite build environment
Run prerendering after other Vite plugins finish their application build hooks
Close React Router's build resources when another plugin's application build hook fails during
react-router build
8.5.0
19 Oct 2026Fix critical CSS collection in dev registering server-only route imports as client dependencies, which triggered dependency re-optimization and full page reloads
Fix intermittent
Prerender: Request failed for ... connect ECONNREFUSEDerrors during prerenderingAdd
ssr: "unstable_api-only"to retain a runtime server for loaders, actions, and route discovery while disabling production document rendering
Patch Changes
Fix critical CSS collection in dev registering server-only route imports as client dependencies, which triggered dependency re-optimization and full page reloads
Fix intermittent
Prerender: Request failed for ... connect ECONNREFUSEDerrors during prerenderingSend requests to the address the Vite preview server bound to
Avoid re-resolving
localhostfor each request, which could select a different address family (127.0.0.1vs::1)
Unstable Changes
⚠️ Unstable features are not recommended for production use
Add
ssr: "unstable_api-only"to retain a runtime server for loaders, actions, and route discovery while disabling production document renderingGenerate a root-only SPA shell when prerendering is disabled
Support prerendered pages and data files alongside runtime loaders and actions, with a SPA fallback for non-prerendered paths
Default API-only builds to lazy route discovery
Reject API-only configuration in RSC Framework Mode
Preserve server-only route exports in additional Vite server environments in both API-only and SSR modes
Serve prerendered pages and the SPA fallback in Vite preview while retaining live data requests and route discovery
Add the
future.unstable_customRouteDiscoveryflag to opt into application-controlled route discovery in conventional Framework ModeFix source maps for route modules in unstable RSC Framework Mode
Add
unstable_apiServerOriginto configure the origin for API-only loader, action, and route discovery requests
8.4.0
15 Sep 2026Fix action submissions behind an HTTPS reverse proxy in
react-router devandvite previewby usingX-Forwarded-Protowhen constructingrequest.urlPass development conditions as CLI flags when relaunching the dev process
Fix stack trace locations for split route modules when source maps are enabled in the
reactRouterVite plugin
Patch Changes
Fix action submissions behind an HTTPS reverse proxy in
react-router devandvite previewby usingX-Forwarded-Protowhen constructingrequest.urlNo React Router configuration is required
The URL host continues to come from
Host, notX-Forwarded-HostConfigure reverse proxies to overwrite client-supplied
X-Forwarded-ProtoheadersDo not expose dev or preview servers publicly
Pass development conditions as CLI flags when relaunching the dev process
Fix stack trace locations for split route modules when source maps are enabled in the
reactRouterVite plugin
8.3.1
28 Aug 2026Bump
@remix-run/node-fetch-serverdependencyGenerate JavaScript entry files at package build time so
react-router reveal --no-typescriptdoes not require Prettier at runtime
Patch Changes
Bump
@remix-run/node-fetch-serverdependencyGenerate JavaScript entry files at package build time so
react-router reveal --no-typescriptdoes not require Prettier at runtimeDeprecate the
--no-typescriptflag ahead of its removal in React Router v9
8.3.0
22 Jul 2026Restart
react-router devwith--conditions=developmentwhen not already configuredAllow
typescript@7to be usedAdd
unstable_rsc/client-versionclient build version virtual module
Minor Changes
Restart
react-router devwith--conditions=developmentwhen not already configured
Patch Changes
Allow
typescript@7to be used
Unstable Changes
⚠️ Unstable features are not recommended for production use
Add
unstable_rsc/client-versionclient build version virtual moduleSupport the
subResourceIntegrityconfig option in RSC Framework Mode
Migration guide
No changes are required when using the default RSC SSR entry. If you maintain a custom
app/entry.ssr.tsx, import the new virtual module and pass its hashes to React'simportMaprender option:+import subResourceIntegrity from "virtual:react-router/unstable_rsc/subresource-integrity"; return renderToReadableStream(<RSCStaticRouter getPayload={getPayload} />, { ...options, bootstrapScriptContent, formState, + importMap: subResourceIntegrity + ? { integrity: subResourceIntegrity } + : undefined, signal: request.signal, });8.2.0
8 Jul 2026Add a Web Streams default server entry for non-Node Framework mode apps
Detect
nubas a supported package manager when installing framework dependenciesDetect user
rolldownOptionsconfig in Vite 8+
Minor Changes
Add a Web Streams default server entry for non-Node Framework mode apps
Apps using
@react-router/node,@react-router/express, or@react-router/servecontinue to use therenderToPipeableStreamdefault server entryApps without those Node server adapter dependencies use a
renderToReadableStreamdefault server entryNon-Node apps with their own
entry.server.tsxmay be able to remove it in favor of the default if it is not doing anything custom
Detect
nubas a supported package manager when installing framework dependencies
Patch Changes
Detect user
rolldownOptionsconfig in Vite 8+
Unstable Changes
⚠️ Unstable features are not recommended for production use
Add the
future.unstable_enableNodeReadableStreamflag to opt Node Framework mode apps into usingrenderToReadableStreaminstead ofrenderToPipeableStreamThis flag has no effect if you have your own
entry.server.tsx
8.1.0
29 Jun 2026Fix a regression with the new prerendering plugin where the
react-router.config.tsbuildEndhook would run before prerendering was completedFixed
react-router typegencrashes under the Bun runtime when Babel default imports are already unwrappedReplace the deprecated
envFile:falseVite config withenvDir:falseto eliminate a deprecation warning when using vite@8.1.0+
Patch Changes
Fix a regression with the new prerendering plugin where the
react-router.config.tsbuildEndhook would run before prerendering was completedFixed
react-router typegencrashes under the Bun runtime when Babel default imports are already unwrappedReplace the deprecated
envFile:falseVite config withenvDir:falseto eliminate a deprecation warning when using vite@8.1.0+Only add the
"node"Vite server condition for Framework mode apps that declare a Node server adapter dependencyThis prevents non-Node SSR runtimes from resolving Node-specific package exports by default
8.0.1
18 Jun 2026Only updates dependencies:react-router 8.0.1@react-router/node 8.0.1@react-router/serve 8.0.1
8.0.0
17 Jun 2026- Breaking
Remove
@react-router/dev/vite/cloudflaredev proxy export; use@cloudflare/vite-plugininstead - Breaking
Remove the
future.v8_trailingSlashAwareDataRequestsflag - Breaking
Remove
future.v8_passThroughRequestsflag - the raw incomingrequestis now always passed through toloader/action.
Major Changes
- Breaking
Remove
@react-router/dev/vite/cloudflaredev proxy export; use@cloudflare/vite-plugininsteadDrops support for
wrangler@3as a peer dependency of@react-router/dev
- Breaking
Remove the
future.v8_trailingSlashAwareDataRequestsflagTrailing slash-aware data request URLs are now the default behavior.
- Breaking
Remove
future.v8_passThroughRequestsflag - the raw incomingrequestis now always passed through toloader/action. - Breaking
Move
future.v8_splitRouteModulesto a top-levelsplitRouteModulesconfig option and change the default behavior totrueSet
splitRouteModules: falseto keep route modules in a single chunkSet
splitRouteModules: "enforce"to require all routes to be splittable
- Breaking
Update minimum Node version to 22.22.0
- Breaking
Require Vite 7+ and make the Vite Environment API build path mandatory
- Breaking
Removed the
future.v8_viteEnvironmentApiflag because the Vite Environment API is always enabled - Breaking
Removed the
future.unstable_previewServerPrerenderingflag and make prerendering with the Vite Environment API the default.
Minor Changes
Bump dependencies
Bumped
@babel/corefrom^7.27.7to^7.29.7Bumped
@babel/generatorfrom^7.27.5to^7.29.7Bumped
@babel/parserfrom^7.27.7to^7.29.7Bumped
@babel/plugin-syntax-jsxfrom^7.27.1to^7.29.7Bumped
@babel/preset-typescriptfrom^7.27.1to^7.29.7Bumped
@babel/traversefrom^7.27.7to^7.29.7Bumped
@babel/typesfrom^7.27.7to^7.29.7Bumped
dedentfrom^1.5.3to^1.7.2Bumped
jsescfrom3.0.2to3.1.0Bumped
lodashfrom^4.17.21to^4.18.1Bumped
prettierfrom^3.6.2to^3.8.3Bumped
@remix-run/node-fetch-serverfrom^0.13.0to^0.13.3Bumped
react-refreshfrom^0.14.0to^0.18.0Bumped
semverfrom^7.3.7to^7.8.1Bumped
tinyglobbyfrom^0.2.14to^0.2.16Bumped
valibotfrom^1.2.0to^1.4.1
Replace
cookieandset-cookie-parserwithcookie-es- Removed
Removed the
vite-nodedependency in favor of Vite's native module runner APIs
Patch Changes
Bump dependencies
Bumped
@babel/corefrom^7.29.0to^7.29.7Bumped
@babel/generatorfrom^7.29.1to^7.29.7Bumped
@babel/parserfrom^7.29.3to^7.29.7Bumped
@babel/plugin-syntax-jsxfrom^7.28.6to^7.29.7Bumped
@babel/preset-typescriptfrom^7.28.5to^7.29.7Bumped
@babel/traversefrom^7.29.0to^7.29.7Bumped
@babel/typesfrom^7.29.0to^7.29.7Bumped
babel-dead-code-eliminationfrom^1.0.6to^1.0.12Bumped
chokidarfrom^4.0.0to^5.0.0Bumped
es-module-lexerfrom^1.3.1to^2.1.0Bumped
exit-hookfrom2.2.1to5.1.0Bumped
isbotfrom^5.1.11to^5.1.40Bumped
p-mapfrom^7.0.3to^7.0.4Bumped
pathefrom^1.1.2to^2.0.3Bumped
pkg-typesfrom^2.3.0to^2.3.1Bumped
react-refreshfrom^0.14.0to^0.18.0Bumped
semverfrom^7.8.0to^7.8.1Bumped
tinyglobbyfrom^0.2.14to^0.2.16Bumped
valibotfrom^1.4.0to^1.4.1
Fix Windows libuv assertion (
!(handle->flags & UV_HANDLE_CLOSING)insrc/win/async.c) during prerendering by usingnode:httpinstead offetchfor internal prerender requests against the Vite preview server
- 7.x
7.18.2
28 Jul 2026Reading the note…
7.18.1
29 Jun 2026Reading the note…
7.18.0
16 Jun 2026Reading the note…
7.17.0
4 Jun 2026Reading the note…
7.16.0
28 May 2026Reading the note…
7.15.1
14 May 2026Reading the note…
7.15.0
5 May 2026Reading the note…
7.14.2
21 Apr 2026Reading the note…
7.14.1
13 Apr 2026Reading the note…
7.14.0
2 Apr 2026Reading the note…
7.13.2
23 Mar 2026Reading the note…
7.13.1
23 Feb 2026Reading the note…
7.13.0
23 Jan 2026Reading the note…
7.12.0
7 Jan 2026Reading the note…
7.11.0
17 Dec 2025Reading the note…
7.10.1
4 Dec 2025Reading the note…
7.10.0
2 Dec 2025Reading the note…
7.9.6
13 Nov 2025Reading the note…
7.9.5
29 Oct 2025Reading the note…
7.9.4
8 Oct 2025Reading the note…
7.9.3
26 Sep 2025Reading the note…
7.9.2
24 Sep 2025Reading the note…
7.9.1
12 Sep 2025Reading the note…
7.9.0
12 Sep 2025Reading the note…
7.8.2
22 Aug 2025Reading the note…
7.8.1
15 Aug 2025Reading the note…
7.8.0
7 Aug 2025Reading the note…
7.7.1
24 Jul 2025Reading the note…
7.7.0
16 Jul 2025Reading the note…
7.6.3
27 Jun 2025Reading the note…
7.6.2
3 Jun 2025Reading the note…
7.6.1
25 May 2025Reading the note…
7.6.0
8 May 2025Reading the note…
7.5.3
28 Apr 2025Reading the note…
7.5.2
24 Apr 2025Reading the note…
7.5.1
17 Apr 2025Reading the note…
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.