Remix Release Notes

Name: Remix
Brand: Remix

Last updated: Apr 3, 2026

Get this feed: RSS Email API CSV MCP Slack n8n Zapier

Remix Products

React Router

62 release notes

All Remix Release Notes (62)

Apr 2, 2026
- Date parsed from source:
  Apr 2, 2026
- First seen by Releasebot:
  Apr 3, 2026
React Router by Remix

v7.14.0

React Router releases v7.14.0 with Vite 8 support, safer Turbo Stream handling for large payloads and memory leaks, and new dev tooling for prerendering multiple server bundles. It also expands unstable RSC Framework Mode with pre-rendering, SPA support, link prefetching, and new route exports.
Minor Changes

Add support for Vite 8 (#14876)

Patch Changes

react-router - Remove recursion from vendored turbo-stream v2 implementation allowing for encoding/decoding of large payloads (#14838)

react-router - Fix encodeViaTurboStream memory leak via unremoved AbortSignal listener (#14900)

@react-router/dev - Support for prerendering multiple server bundles with v8_viteEnvironmentApi (#14921)

Unstable Changes

⚠️ Unstable features are not recommended for production use

@react-router/dev - Pre-rendering and SPA Mode support for RSC Framework Mode (#14907)

@react-router/dev - Update react-router reveal to support RSC Framework Mode for entry.client, entry.rsc, entry.ssr (#14904)

react-router - Support in RSC Framework Mode (#14902)

react-router - Add support for new route module exports in unstable RSC Framework Mode (#14901)

⚠️ This is a breaking change if you have already adopted RSC Framework Mode in it's unstable state - you will need to update your route modules to export the new annotations

The following route module components have their own mutually exclusive server component counterparts:

Client Component export | Server Component export
default | ServerComponent
ErrorBoundary | ServerErrorBoundary
Layout | ServerLayout
HydrateFallback | ServerHydrateFallback

If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also implicitly server components

If you want to keep those as server components - rename them and prefix them with Server

If you were previously importing the implementations of those components from a client module, you can inline them

Full Changelog: v7.13.2...v7.14.0
Original source Report a problem
Mar 23, 2026
- Date parsed from source:
  Mar 23, 2026
- First seen by Releasebot:
  Mar 23, 2026
React Router by Remix

v7.13.2

React Router adds unstable pass-through request support and a new unstable_url parameter for route handlers, improving access to raw and normalized URLs while reducing server-side overhead. This release also includes patch fixes for hydration, path navigation, dev crashes, and redirects.
What's Changed

Pass-through Requests (unstable)

By default, React Router normalizes the request.url passed to your loader, action, and middleware functions by removing React Router's internal implementation details (.data suffixes, index + _routes query params). This release introduces a new future.unstable_passThroughRequests flag to disable this normalization and pass the raw HTTP request instance to your handlers.

In addition to reducing server-side overhead by eliminating multiple new Request() calls on the critical path, this also provides additional visibility to your route handlers/instrumentations allowing you to differentiate document from data requests.

If you were previously relying on the normalization of request.url, you can switch to use the new sibling unstable_url parameter which contains a URL instance representing the normalized location:

// ❌ Before: you could assume there was no `.data` suffix in `request.url` export async function loader({ request }: Route.LoaderArgs) { let url = new URL(request.url); if (url.pathname === "/path") { // This check will fail with the flag enabled because the `.data` suffix will // exist on data requests } } // ✅ After: use `unstable_url` for normalized routing logic and `request.url` // for raw routing logic export async function loader({ request, unstable_url }: Route.LoaderArgs) { if (unstable_url.pathname === "/path") { // This will always have the `.data` suffix stripped } // And now you can distinguish between document versus data requests let isDataRequest = new URL(request.url).pathname.endsWith(".data"); }

Route handlers/middleware unstable_url parameter

We have added a new unstable_url: URL parameter to route handler methods (loader, action, middleware, etc.) that contains the normalized URL the application is navigating to or fetching with React Router implementation details removed (.data suffix, index / _routes query params).

This parameter is primarily needed when adopting the new future.unstable_passthroughRequests future flag as a way to continue accessing the normalized URL. If you don't have the flag enabled, then unstable_url will match request.url.

Patch Changes

react-router - Fix clientLoader.hydrate when an ancestor route is also hydrating a clientLoader (#14835)

react-router - Fix type error when passing Framework Mode route components using Route.ComponentProps to createRoutesStub (#14892)

react-router - Fix percent encoding in relative path navigation (#14786)

react-router - Internal refactor to consolidate framework-agnostic/React-specific route type layers - no public API changes (#14765)

@react-router/dev - Fix react-router dev crash when Unix socket files exist in the project root (#14854)

@react-router/dev - Escape redirect locations in pre-rendered redirect HTML (#14880)

create-react-router - replace chalk with picocolors (#14837)

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - Sync protocol validation to RSC flows (#14882)

react-router - Add future.unstable_passThroughRequests flag (#14775)

react-router - Add a new unstable_url: URL parameter to route handler methods (loader, action, middleware, etc.) representing the normalized URL the application is navigating to or fetching, with React Router implementation details removed (.data suffix, index / _routes query params) (#14775)

Full Changelog: v7.13.1...v7.13.2
Original source Report a problem
All of your release notes in one feed

Join Releasebot and get updates from Remix and hundreds of other software products.

Create account
Get updates with: RSS Email API CSV MCP Slack n8n Zapier
Feb 23, 2026
- Date parsed from source:
  Feb 23, 2026
- First seen by Releasebot:
  Feb 24, 2026
- Modified by Releasebot:
  Mar 2, 2026
React Router by Remix

v7.13.1

New unstable URL masking API in Framework/Data Mode enables masked browser URLs for contextual routing and modal experiences. The release also includes several patch fixes and RSC unstable features aimed at improving routing, error handling, and cross‑mode parity. A notable upgrade bridging Declarative and Data modes.
What's Changed

URL Masking (unstable)
This release includes a new API which brings first-class support for URL masking to Framework/Data Mode (RFC). This allows the same type of UI you could achieve in Declarative Mode via manual backgroundLocation management. That example has been converted to Data Mode using the new API here.

Patch Changes

react-router - Clear timeout when turbo-stream encoding completes (#14810)

react-router - Improve error message when Origin header is invalid (#14743)

react-router - Fix matchPath optional params matching without a "/" separator. (#14689)

matchPath("/users/:id?", "/usersblah") now returns null

matchPath("/test_route/:part?", "/test_route_more") now returns null.

react-router - Fix HydrateFallback rendering during initial lazy route discovery with matching splat route (#14740)

react-router - Preserve query parameters and hash on manifest version mismatch reload (#14813)

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - RSC: fix null reference exception in bad codepath leading to invalid route tree comparisons (#14780)

react-router - RSC: add unstable_getRequest API (#14758)

react-router - RSC: Update failed origin checks to return a 400 status and appropriate UI instead of a generic 500 (#14755)

react-router - Add support for in Framework/Data Mode which allows users to navigate to a URL in the router but "mask" the URL displayed in the browser (#14716)

This is useful for contextual routing usages such as displaying an image in a modal on top of a gallery, but displaying a browser URL directly to the image that can be shared and loaded without the contextual gallery in the background

The masked location, if present, will be available on useLocation().unstable_mask so you can detect whether you are currently masked or not

Masked URLs only work for SPA use cases, and will be removed from history.state during SSR

This provides a first-class API to mask URLs in Framework/Data Mode to achieve the same behavior you could do in Declarative Mode via manual backgroundLocation management.

Full Changelog: v7.13.0...v7.13.1
Original source Report a problem
Jan 23, 2026
- Date parsed from source:
  Jan 23, 2026
- First seen by Releasebot:
  Jan 24, 2026
React Router by Remix

v7.13.0

React Router 7.13.0 brings a new crossOrigin prop for Links along with a host of fixes to navigation, origin checks, nonce handling, and route file handling. The update tightens behavior and improves reliability across edge cases.
Minor Changes

react-router - Add crossOrigin prop to Links component (#14687)

Patch Changes

react-router - Fix double slash normalization for useNavigate paths with a colon (#14718)

react-router - Fix missing nonce on inline criticalCss (#14691)

react-router - Update failed origin checks to return a 400 status instead of a 500 (#14737)

react-router - Loosen allowedActionOrigins glob check so ** matches all domains (#14722)

@react-router/dev - Bump @remix-run/node-fetch-server dep (#14704)

@react-router/fs-routes - Fix route file paths when routes directory is outside of the app directory (#13937)

Full Changelog: v7.12.0...v7.13.0
Original source Report a problem
Jan 7, 2026
- Date parsed from source:
  Jan 7, 2026
- First seen by Releasebot:
  Jan 9, 2026
React Router by Remix

v6.30.3
Patch Changes

Validate redirect locations (#14707)

Full Changelog: v6.30.2...v6.30.3
Original source Report a problem
Jan 7, 2026
- Date parsed from source:
  Jan 7, 2026
- First seen by Releasebot:
  Jan 8, 2026
- Modified by Releasebot:
  Jan 28, 2026
React Router by Remix

v7.12.0

Release notes announce security hardening and bug fixes for React Router, including CSRF protection, safe redirect validation, and SSR/XSS fixes. It adds config options and fixes for generatePath and scroll restoration, with unstable features to aid migration.
Security Notice

This release addresses 3 security vulnerabilities:

CSRF in React Router Action/Server Action Request Processing

XSS via Open Redirects

React Router SSR XSS in ScrollRestoration

Minor Changes

react-router - Add additional layer of CSRF protection by rejecting submissions to UI routes from external origins (#14708)

If you need to permit access to specific external origins, there is a new allowedActionOrigins config field in react-router.config.ts where you can specify external origins

Patch Changes

react-router - Fix generatePath when used with suffixed params (i.e., /books/:id.json) (#14269)

react-router - Escape HTML in scroll restoration keys (#14705)

react-router - Validate redirect locations (#14706)

@react-router/dev - Fix Maximum call stack size exceeded errors when HMR is triggered against code with cyclic imports (#14522)

@react-router/dev - Skip SSR middleware in vite preview server for SPA mode (#14673)

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - Preserve clientLoader.hydrate=true when using (#14674)

react-router - Pass value through to the underlying importmap script tag when using future.unstable_subResourceIntegrity (#14675)

react-router - Export UNSAFE_createMemoryHistory and UNSAFE_createHashHistory alongside UNSAFE_createBrowserHistory for consistency (#14663)

These are not intended to be used for new apps but intended to help apps using unstable_HistoryRouter migrate from v6->v7 so they can adopt the newer APIs

@react-router/dev - Add a new future.unstable_trailingSlashAwareDataRequests flag to provide consistent behavior of request.pathname inside middleware, loader, and action functions on document and data requests when a trailing slash is present in the browser URL. (#14644)

Currently, your HTTP and request pathnames would be as follows for /a/b/c and /a/b/c/

With this flag enabled, these pathnames will be made consistent though a new _.data format for client-side .data requests

This a bug fix but we are putting it behind an opt-in flag because it has the potential to be a "breaking bug fix" if you are relying on the URL format for any other application or caching logic

Enabling this flag also changes the format of client side .data requests from /root.data to /.data when navigating to / to align with the new format - This does not impact the request pathname which is still / in all cases

Full Changelog: v7.11.0...v7.12.0
Original source Report a problem
Dec 17, 2025
- Date parsed from source:
  Dec 17, 2025
- First seen by Releasebot:
  Dec 18, 2025
- Modified by Releasebot:
  Jan 9, 2026
React Router by Remix

v7.11.0

React Router 7.x brings vite preview support and stabilized client-side onError APIs for easier error handling. It adds an unstable call-site revalidation opt-out and several stability fixes plus experimental features for early testing.
What's Changed

vite preview Support

We've added support for vite preview when using Framework mode to make it easy to preview your production build.

Stabilized Client-side onError

The existing / APIs have been stabilized as / . Please see the Error Reporting docs for more information.

Call-site Revalidation Opt-out (unstable)

We've added initial unstable support for call-site revalidation opt-out via a new unstable_defaultShouldRevalidate flag (RFC). This flag is available on all navigation/fetcher submission APIs to alter standard revalidation behavior. If any routes include a shouldRevalidate function, then the flag value will be passed to that function so the route has the final say on revalidation behavior.
This flag is also available on non-submission navigational use cases - for example, you may want to opt-out of revalidation when adding a search param that doesn't impact the UI:
This flag is also available on non-submission navigational use cases - for example, you may want to opt-out of revalidation when adding a search param that doesn't impact the UI:

Minor Changes

react-router - Stabilize / (#14546)

@react-router/dev - Add vite preview support (#14507)

Patch Changes

react-router - Fix unstable_useTransitions prop on component to permit omission for backwards compatibility (#14646)

react-router - Allow redirects to be returned from client side middleware (#14598)

react-router - Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#14627)

@react-router/serve - Update compression and morgan dependencies to address on-headers CVE: GHSA-76c9-3jph-rj3q (#14652)

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - RSC: Support for throwing data() and Response from server component render phase (#14632)

Response body is not serialized as async work is not allowed as error encoding phase.

If you wish to transmit data to the boundary, throw data() instead

react-router - RSC: Support for throwing redirect Response's at render time (#14596)

react-router - RSC: routeRSCServerRequest replace fetchServer with serverResponse (#14597)

@react-router/dev - RSC (Framework mode): Manual chunking for react and react-router deps (#14655)

@react-router/dev - RSC (Framework mode): Optimize react-server-dom-webpack if in project package.json (#14656)

@react-router/dev - RSC (Framework mode): Support custom entrypoints (#14643)

react-router - Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors (#14542)

Full Changelog: v7.10.1...v7.11.0
Original source Report a problem
Dec 4, 2025
- Date parsed from source:
  Dec 4, 2025
- First seen by Releasebot:
  Dec 9, 2025
React Router by Remix

v7.10.1
Patch Changes

react-router - Update the useOptimistic stub we provide for React 18 users to use a stable setter function to avoid potential useEffect loops - specifically when using (#14628)

@react-router/dev - Import ESM package pkg-types with a dynamic import() to fix issues on Node 20.18 (#14624)

@react-router/dev - Update valibot dependency to ^1.2.0 to address GHSA-vqpr-j7v3-hqw9 (#14608)

Full Changelog: v7.10.0...v7.10.1
Original source Report a problem
Dec 2, 2025
- Date parsed from source:
  Dec 2, 2025
- First seen by Releasebot:
  Dec 9, 2025
- Modified by Releasebot:
  Jan 28, 2026
React Router by Remix

v7.10.0

React Router ships a stable API refresh with renamed flags and stabilized fetcher.reset and data strategy hooks. It includes multiple patches, a few unstable feature notes, and core fixes plus a version bump from v7.9.6 to v7.10.0 for broader release readiness.
What's Changed

We've stabilized a handful of existing APIs and future flags in this release, please make the appropriate changes if you'd adopted any of these APIs in their unstable state!

Stabilized future.v8_splitRouteModules

The existing future.unstable_splitRouteModules flag has been stabilized as future.v8_splitRouteModules in react-router.config.ts. Please see the docs for more information on adopting this flag.

Stabilized future.v8_viteEnvironmentApi

The existing future.unstable_viteEnvironmentApi flag has been stabilized as future.v8_viteEnvironmentApi in react-router.config.ts. Please see the docs for more information on adopting this flag.

Stabilized fetcher.reset()

The existing fetcher.unstable_reset() API has been stabilized as fetcher.reset().

Stabilized DataStrategyMatch.shouldCallHandler()

The existing low-level DataStrategyMatch.unstable_shouldCallHandler() / DataStrategyMatch.unstable_shouldRevalidateArgs APIs have been stabilized as DataStrategyMatch.shouldCallHandler() / DataStrategyMatch.shouldRevalidateArgs. Please see the docs for information about using a custom dataStrategy and how to migrate away from the deprecated DataStrategyMatch.shouldLoad API if you are using that today.

Minor Changes

react-router - Stabilize fetcher.reset() (#14545)

react-router - Stabilize the dataStrategy match.shouldCallHandler() / match.shouldRevalidateArgs APIs (#14592)

@react-router/dev - Stabilize future.v8_splitRouteModules, replacing future.unstable_splitRouteModules (#14595)

@react-router/dev - Stabilize future.v8_viteEnvironmentApi, replacing future.unstable_viteEnvironmentApi (#14595)

Patch Changes

react-router - Fix a Framework Mode bug where the defaultShouldRevalidate parameter to shouldRevalidate would not be correct after action returned a 4xx/5xx response (true when it should have been false) (#14592)

react-router - Fix fetcher.submit failing with plain objects containing a tagName property (#14534)

react-router - Fix the promise returned from useNavigate in Framework/Data Mode so that it properly tracks the duration of popstate navigations (i.e., navigate(-1)) (#14524)

react-router - Preserve statusText on the ErrorResponse instance when throwing data() from a route handler (#14555)

react-router - Optimize href() to avoid backtracking regex on splat (#14329)

@react-router/dev - Fix internal type error in useRoute types that surfaces when skipLibCheck is disabled (#14577)

@react-router/dev - Load environment variables before evaluating routes.ts (#14446)

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - Add unstable_pattern to the parameters for client side unstable_onError (#14573)

react-router - Refactor how unstable_onError is called internally by RouterProvider to avoid potential strict mode issues (#14573)

react-router - Add new unstable_useTransitions flag to routers to give users control over the usage of React.startTransition and React.useOptimistic (#14524)

Full Changelog: v7.9.6...v7.10.0
Original source Report a problem
Nov 13, 2025
- Date parsed from source:
  Nov 13, 2025
- First seen by Releasebot:
  Jan 9, 2026
React Router by Remix

v6.30.2
Patch Changes

Normalize double-slashes in resolvePath (#14537)

Full Changelog: v6.30.1...v6.30.2
Original source Report a problem

Remix Release Notes

Remix Products

All Remix Release Notes (62)

v7.14.0

Minor Changes

Patch Changes

Unstable Changes

v7.13.2

What's Changed

Pass-through Requests (unstable)

Route handlers/middleware unstable_url parameter

Patch Changes

Unstable Changes

v7.13.1

What's Changed

Patch Changes

Unstable Changes

v7.13.0

Minor Changes

Patch Changes

Full Changelog: v7.12.0...v7.13.0

v6.30.3

Patch Changes

v7.12.0

Security Notice

Minor Changes

Patch Changes

Unstable Changes

Full Changelog: v7.11.0...v7.12.0

v7.11.0

What's Changed

vite preview Support

Stabilized Client-side onError

Call-site Revalidation Opt-out (unstable)

Minor Changes

Patch Changes

Unstable Changes

Full Changelog: v7.10.1...v7.11.0

v7.10.1

Patch Changes

Full Changelog: v7.10.0...v7.10.1

v7.10.0

What's Changed

Stabilized future.v8_splitRouteModules

Stabilized future.v8_viteEnvironmentApi

Stabilized fetcher.reset()

Stabilized DataStrategyMatch.shouldCallHandler()

Minor Changes

Patch Changes

Unstable Changes

v6.30.2

Patch Changes

Related vendors