# Table of Contents

- [React Router Home  | React Router](#react-router-home-react-router)
- [React Router Home v7.6.0 | React Router](#react-router-home-v7-6-0-react-router)
- [Docs v6.30.0 | React Router](#docs-v6-30-0-react-router)
- [Picking a Mode  | React Router](#picking-a-mode-react-router)
- [Installation  | React Router](#installation-react-router)
- [Routing  | React Router](#routing-react-router)
- [Route Module  | React Router](#route-module-react-router)
- [Data Loading  | React Router](#data-loading-react-router)
- [Rendering Strategies  | React Router](#rendering-strategies-react-router)
- [Actions  | React Router](#actions-react-router)
- [CHANGELOG.md  | React Router](#changelog-md-react-router)
- [Navigating  | React Router](#navigating-react-router)
- [Pending UI  | React Router](#pending-ui-react-router)
- [React Router Home (dev branch) | React Router](#react-router-home-dev-branch-react-router)
- [Testing  | React Router](#testing-react-router)
- [Deploying  | React Router](#deploying-react-router)
- [Installation  | React Router](#installation-react-router)
- [Routing  | React Router](#routing-react-router)
- [CHANGELOG.md v7.6.0 | React Router](#changelog-md-v7-6-0-react-router)
- [Routing v7.6.0 | React Router](#routing-v7-6-0-react-router)
- [Tutorial v6.30.0 | React Router](#tutorial-v6-30-0-react-router)
- [Examples v6.30.0 | React Router](#examples-v6-30-0-react-router)
- [Navigating  | React Router](#navigating-react-router)
- [Actions  | React Router](#actions-react-router)

---

# React Router Home  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/home)
[dev](/dev/)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

React Router Home

[](#react-router-home)
React Router Home
========================================

React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. You can use it maximally as a React framework or as minimally as you want.

[](#getting-started)
Getting Started
------------------------------------

There are three primary ways, or "modes", to use it in your app, so there are three guides to get you started.

*   [Declarative](./start/declarative/installation)
    
*   [Data](./start/data/custom)
    
*   [Framework](./start/framework/installation)
    

Learn which mode is right for you in [Picking a Mode](./start/modes)
.

[](#using-these-guides)
Using These Guides
------------------------------------------

Across the docs you'll see the following icons:

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Available with Declarative")
    

These icons indicate which mode the content is relevant to.

Additional auto-generated reference documentation is available:

[Autogenerated Reference Docs ↗](https://api.reactrouter.com/v7/modules/react_router.html)

[](#upgrading)
Upgrading
------------------------

If you are caught up on future flags, upgrading from React Router v6 or Remix v2 is generally non-breaking. Remix v2 apps are encouraged to upgrade to React Router v7.

*   [Upgrade from v6](./upgrading/v6)
    
*   [Upgrade from Remix](./upgrading/remix)
    

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/index.md)

---

# React Router Home v7.6.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

7.6.0

Branches

[latest (7.6.0)](/home)
[dev](/dev/home)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

React Router Home

[](#react-router-home)
React Router Home
========================================

React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. You can use it maximally as a React framework or as minimally as you want.

[](#getting-started)
Getting Started
------------------------------------

There are three primary ways, or "modes", to use it in your app, so there are three guides to get you started.

*   [Declarative](./start/declarative/installation)
    
*   [Data](./start/data/custom)
    
*   [Framework](./start/framework/installation)
    

Learn which mode is right for you in [Picking a Mode](./start/modes)
.

[](#using-these-guides)
Using These Guides
------------------------------------------

Across the docs you'll see the following icons:

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Available with Declarative")
    

These icons indicate which mode the content is relevant to.

Additional auto-generated reference documentation is available:

[Autogenerated Reference Docs ↗](https://api.reactrouter.com/v7/modules/react_router.html)

[](#upgrading)
Upgrading
------------------------

If you are caught up on future flags, upgrading from React Router v6 or Remix v2 is generally non-breaking. Remix v2 apps are encouraged to upgrade to React Router v7.

*   [Upgrade from v6](./upgrading/v6)
    
*   [Upgrade from Remix](./upgrading/remix)
    

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Docs v6.30.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

6.30.0

Branches

[latest (7.6.0)](/home)
[dev](/dev/)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Navigation

[What's New in 6.4?\
------------------\
\
v6.4 is our most exciting release yet with new data abstractions for reads, writes, and navigation hooks to easily keep your UI in sync with your data. The new feature overview will catch you up.](/6.30.0/start/overview)
[I'm New!\
--------\
\
Start with the tutorial. It will quickly introduce you to the primary features of React Router: from configuring routes, to loading and mutating data, to pending and optimistic UI.](/6.30.0/start/tutorial)
[I'm on v5\
---------\
\
The migration guide will help you migrate incrementally and keep shipping along the way. Or, do it all in one yolo commit! Either way, we've got you covered to start using the new features right away.](/6.30.0/upgrading/v5)
[I'm Stuck!\
----------\
\
Running into a problem? Chances are you're not the first! Explore common questions about React Router v6.](/6.30.0/start/faq)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Picking a Mode  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/modes)
[dev](/dev/start/modes)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Picking a Mode

[](#picking-a-mode)
Picking a Mode
==================================

React Router is a multi-strategy router for React. There are three primary ways, or "modes", to use it in your app. Across the docs you'll see these icons indicating which mode the content is relevant to:

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Available with Declarative")
    

The features available in each mode are additive, so moving from Declarative to Data to Framework simply adds more features at the cost of architectural control. So pick your mode based on how much control or how much help you want from React Router.

The mode depends on which "top level" router API you're using:

**Declarative**

Declarative mode enables basic routing features like matching URLs to components, navigating around the app, and providing active states with APIs like `<Link>`, `useNavigate`, and `useLocation`.

    import { BrowserRouter } from "react-router";
    
    ReactDOM.createRoot(root).render(
      <BrowserRouter>
        <App />
      </BrowserRouter>
    );
    

**Data**

By moving route configuration outside of React rendering, Data Mode adds data loading, actions, pending states and more with APIs like `loader`, `action`, and `useFetcher`.

    import {
      createBrowserRouter,
      RouterProvider,
    } from "react-router";
    
    let router = createBrowserRouter([\
      {\
        path: "/",\
        Component: Root,\
        loader: loadRootData,\
      },\
    ]);
    
    ReactDOM.createRoot(root).render(
      <RouterProvider router={router} />
    );
    

**Framework**

Framework Mode wraps Data Mode with a Vite plugin to add the full React Router experience with:

*   typesafe `href`
*   typesafe Route Module API
*   intelligent code splitting
*   SPA, SSR, and static rendering strategies
*   and more

    import { index, route } from "@react-router/dev/routes";
    
    export default [\
      index("./home.tsx"),\
      route("products/:pid", "./product.tsx"),\
    ];
    

You'll then have access to the Route Module API with typesafe params, loaderData, code splitting, SPA/SSR/SSG strategies, and more.

    import { Route } from "+./types/product.tsx";
    
    export async function loader({ params }: Route.LoaderArgs) {
      let product = await getProduct(params.pid);
      return { product };
    }
    
    export default function Product({
      loaderData,
    }: Route.ComponentProps) {
      return <div>{loaderData.product.name}</div>;
    }
    

[](#decision-advice)
Decision Advice
------------------------------------

Every mode supports any architecture and deployment target, so the question isn't really about if you want SSR, SPA, etc. It's about how much you want to do yourself.

**Use Framework Mode if you:**

*   are too new to have an opinion
*   are considering Next.js, Solid Start, SvelteKit, Astro, TanStack Start, etc. and want to compare
*   just want to build something with React
*   might want to server render, might not
*   are coming from Remix (React Router v7 is the "next version" after Remix v2)
*   are migrating from Next.js

[→ Get Started with Framework Mode](./framework/installation)
.

**Use Data Mode if you:**

*   want data features but also want to have control over bundling, data, and server abstractions
*   started a data router in v6.4 and are happy with it

[→ Get Started with Data Mode](./data/custom)
.

**Use Declarative Mode if you:**

*   want to use React Router as simply as possible
*   are coming from v6 and are happy with the `<BrowserRouter>`
*   have a data layer that either skips pending states (like local first, background data replication/sync) or has its own abstractions for them
*   are coming from Create React App (you may want to consider framework mode though)

[→ Get Started with Declarative Mode](./declarative/installation)
.

[](#api--mode-availability-table)
API + Mode Availability Table
---------------------------------------------------------------

This is mostly for the LLMs, but knock yourself out:

| API | Framework | Data | Declarative |
| --- | --- | --- | --- |
| Await | ✅   | ✅   |     |
| Form | ✅   | ✅   |     |
| Link | ✅   | ✅   | ✅   |
| `<Link discover>` | ✅   |     |     |
| `<Link prefetch>` | ✅   |     |     |
| `<Link preventScrollReset>` | ✅   | ✅   |     |
| Links | ✅   |     |     |
| Meta | ✅   |     |     |
| NavLink | ✅   | ✅   | ✅   |
| `<NavLink discover>` | ✅   |     |     |
| `<NavLink prefetch>` | ✅   |     |     |
| `<NavLink preventScrollReset>` | ✅   | ✅   |     |
| NavLink `isPending` | ✅   | ✅   |     |
| Navigate | ✅   | ✅   | ✅   |
| Outlet | ✅   | ✅   | ✅   |
| PrefetchPageLinks | ✅   |     |     |
| Route | ✅   | ✅   | ✅   |
| Routes | ✅   | ✅   | ✅   |
| Scripts | ✅   |     |     |
| ScrollRestoration | ✅   | ✅   |     |
| ServerRouter | ✅   |     |     |
| usePrompt | ✅   | ✅   | ✅   |
| useActionData | ✅   | ✅   |     |
| useAsyncError | ✅   | ✅   |     |
| useAsyncValue | ✅   | ✅   |     |
| useBeforeUnload | ✅   | ✅   | ✅   |
| useBlocker | ✅   | ✅   |     |
| useFetcher | ✅   | ✅   |     |
| useFetchers | ✅   | ✅   |     |
| useFormAction | ✅   | ✅   |     |
| useHref | ✅   | ✅   | ✅   |
| useInRouterContext | ✅   | ✅   | ✅   |
| useLinkClickHandler | ✅   | ✅   | ✅   |
| useLoaderData | ✅   | ✅   |     |
| useLocation | ✅   | ✅   | ✅   |
| useMatch | ✅   | ✅   | ✅   |
| useMatches | ✅   | ✅   |     |
| useNavigate | ✅   | ✅   | ✅   |
| useNavigation | ✅   | ✅   |     |
| useNavigationType | ✅   | ✅   | ✅   |
| useOutlet | ✅   | ✅   | ✅   |
| useOutletContext | ✅   | ✅   | ✅   |
| useParams | ✅   | ✅   | ✅   |
| useResolvedPath | ✅   | ✅   | ✅   |
| useRevalidator | ✅   | ✅   |     |
| useRouteError | ✅   | ✅   |     |
| useRouteLoaderData | ✅   | ✅   |     |
| useRoutes | ✅   | ✅   | ✅   |
| useSearchParams | ✅   | ✅   | ✅   |
| useSubmit | ✅   | ✅   |     |
| useViewTransitionState | ✅   | ✅   |     |
| isCookieFunction | ✅   | ✅   |     |
| isSessionFunction | ✅   | ✅   |     |
| createCookie | ✅   | ✅   |     |
| createCookieSessionStorage | ✅   | ✅   |     |
| createMemorySessionStorage | ✅   | ✅   |     |
| createPath | ✅   | ✅   | ✅   |
| createRoutesStub | ✅   | ✅   |     |
| createSearchParams | ✅   | ✅   | ✅   |
| data | ✅   | ✅   |     |
| generatePath | ✅   | ✅   | ✅   |
| href | ✅   |     |     |
| isCookie | ✅   | ✅   |     |
| isRouteErrorResponse | ✅   | ✅   |     |
| isSession | ✅   | ✅   |     |
| matchPath | ✅   | ✅   | ✅   |
| matchRoutes | ✅   | ✅   | ✅   |
| parsePath | ✅   | ✅   | ✅   |
| redirect | ✅   | ✅   |     |
| redirectDocument | ✅   | ✅   |     |
| renderMatches | ✅   | ✅   | ✅   |
| replace | ✅   | ✅   |     |
| resolvePath | ✅   | ✅   | ✅   |

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/modes.md)

---

# Installation  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/installation)
[dev](/dev/start/framework/installation)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Installation

[](#installation)
Installation
==============================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

Most projects start with a template. Let's use a basic template maintained by React Router:

    npx create-react-router@latest my-react-router-app
    

Now change into the new directory and start the app

    cd my-react-router-app
    npm i
    npm run dev
    

You can now open your browser to `http://localhost:5173`

You can [view the template on GitHub](https://github.com/remix-run/react-router-templates/tree/main/default)
 to see how to manually set up your project.

We also have a number of [ready to deploy templates](https://github.com/remix-run/react-router-templates)
 available for you to get started with:

    npx create-react-router@latest --template remix-run/react-router-templates/<template-name>
    

* * *

Next: [Routing](./routing)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/installation.md)

---

# Routing  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/routing)
[dev](/dev/start/framework/routing)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Routing

On this page

*   [Configuring Routes](/start/framework/routing#configuring-routes)
    
*   [Route Modules](/start/framework/routing#route-modules)
    
*   [Nested Routes](/start/framework/routing#nested-routes)
    
*   [Root Route](/start/framework/routing#root-route)
    
*   [Layout Routes](/start/framework/routing#layout-routes)
    
*   [Index Routes](/start/framework/routing#index-routes)
    
*   [Route Prefixes](/start/framework/routing#route-prefixes)
    
*   [Dynamic Segments](/start/framework/routing#dynamic-segments)
    
*   [Optional Segments](/start/framework/routing#optional-segments)
    
*   [Splats](/start/framework/routing#splats)
    
*   [Component Routes](/start/framework/routing#component-routes)
    

*   [Configuring Routes](/start/framework/routing#configuring-routes)
    
*   [Route Modules](/start/framework/routing#route-modules)
    
*   [Nested Routes](/start/framework/routing#nested-routes)
    
*   [Root Route](/start/framework/routing#root-route)
    
*   [Layout Routes](/start/framework/routing#layout-routes)
    
*   [Index Routes](/start/framework/routing#index-routes)
    
*   [Route Prefixes](/start/framework/routing#route-prefixes)
    
*   [Dynamic Segments](/start/framework/routing#dynamic-segments)
    
*   [Optional Segments](/start/framework/routing#optional-segments)
    
*   [Splats](/start/framework/routing#splats)
    
*   [Component Routes](/start/framework/routing#component-routes)
    

[](#routing)
Routing
====================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#configuring-routes)
Configuring Routes
------------------------------------------

Routes are configured in `app/routes.ts`. Each route has two required parts: a URL pattern to match the URL, and a file path to the route module that defines its behavior.

    import {
      type RouteConfig,
      route,
    } from "@react-router/dev/routes";
    
    export default [\
      route("some/path", "./some/file.tsx"),\
      // pattern ^           ^ module file\
    ] satisfies RouteConfig;
    

Here is a larger sample route config:

    import {
      type RouteConfig,
      route,
      index,
      layout,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      index("./home.tsx"),\
      route("about", "./about.tsx"),\
    \
      layout("./auth/layout.tsx", [\
        route("login", "./auth/login.tsx"),\
        route("register", "./auth/register.tsx"),\
      ]),\
    \
      ...prefix("concerts", [\
        index("./concerts/home.tsx"),\
        route(":city", "./concerts/city.tsx"),\
        route("trending", "./concerts/trending.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

If you prefer to define your routes via file naming conventions rather than configuration, the `@react-router/fs-routes` package provides a [file system routing convention](../../how-to/file-route-conventions)
. You can even combine different routing conventions if you like:

    import {
      type RouteConfig,
      route,
    } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export default [\
      route("/", "./home.tsx"),\
    \
      ...(await flatRoutes()),\
    ] satisfies RouteConfig;
    

[](#route-modules)
Route Modules
--------------------------------

The files referenced in `routes.ts` define each route's behavior:

    route("teams/:teamId", "./team.tsx"),
    //           route module ^^^^^^^^
    

Here's a sample route module:

    // provides type safety/inference
    import type { Route } from "./+types/team";
    
    // provides `loaderData` to the component
    export async function loader({ params }: Route.LoaderArgs) {
      let team = await fetchTeam(params.teamId);
      return { name: team.name };
    }
    
    // renders after the loader is done
    export default function Component({
      loaderData,
    }: Route.ComponentProps) {
      return <h1>{loaderData.name}</h1>;
    }
    

Route modules have more features like actions, headers, and error boundaries, but they will be covered in the next guide: [Route Modules](./route-module)

[](#nested-routes)
Nested Routes
--------------------------------

Routes can be nested inside parent routes.

    import {
      type RouteConfig,
      route,
      index,
    } from "@react-router/dev/routes";
    
    export default [\
      // parent route\
      route("dashboard", "./dashboard.tsx", [\
        // child routes\
        index("./home.tsx"),\
        route("settings", "./settings.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

The path of the parent is automatically included in the child, so this config creates both `"/dashboard"` and `"/dashboard/settings"` URLs.

Child routes are rendered through the `<Outlet/>` in the parent route.

    import { Outlet } from "react-router";
    
    export default function Dashboard() {
      return (
        <div>
          <h1>Dashboard</h1>
          {/* will either be home.tsx or settings.tsx */}
          <Outlet />
        </div>
      );
    }
    

[](#root-route)
Root Route
--------------------------

Every route in `routes.ts` is nested inside the special `app/root.tsx` module.

[](#layout-routes)
Layout Routes
--------------------------------

Using `layout`, layout routes create new nesting for their children, but they don't add any segments to the URL. It's like the root route but they can be added at any level.

    import {
      type RouteConfig,
      route,
      layout,
      index,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      layout("./marketing/layout.tsx", [\
        index("./marketing/home.tsx"),\
        route("contact", "./marketing/contact.tsx"),\
      ]),\
      ...prefix("projects", [\
        index("./projects/home.tsx"),\
        layout("./projects/project-layout.tsx", [\
          route(":pid", "./projects/project.tsx"),\
          route(":pid/edit", "./projects/edit-project.tsx"),\
        ]),\
      ]),\
    ] satisfies RouteConfig;
    

Note that:

*   `home.tsx` and `contact.tsx` will be rendered into the `marketing/layout.tsx` outlet without creating any new URL paths
*   `project.tsx` and `edit-project.tsx` will be rendered into the `projects/project-layout.tsx` outlet at `/projects/:pid` and `/projects/:pid/edit` while `projects/home.tsx` will not.

[](#index-routes)
Index Routes
------------------------------

    index(componentFile),
    

Index routes render into their parent's [Outlet](https://api.reactrouter.com/v7/functions/react_router.Outlet.html)
 at their parent's URL (like a default child route).

    import {
      type RouteConfig,
      route,
      index,
    } from "@react-router/dev/routes";
    
    export default [\
      // renders into the root.tsx Outlet at /\
      index("./home.tsx"),\
      route("dashboard", "./dashboard.tsx", [\
        // renders into the dashboard.tsx Outlet at /dashboard\
        index("./dashboard-home.tsx"),\
        route("settings", "./dashboard-settings.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

Note that index routes can't have children.

[](#route-prefixes)
Route Prefixes
----------------------------------

Using `prefix`, you can add a path prefix to a set of routes without needing to introduce a parent route file.

    import {
      type RouteConfig,
      route,
      layout,
      index,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      layout("./marketing/layout.tsx", [\
        index("./marketing/home.tsx"),\
        route("contact", "./marketing/contact.tsx"),\
      ]),\
      ...prefix("projects", [\
        index("./projects/home.tsx"),\
        layout("./projects/project-layout.tsx", [\
          route(":pid", "./projects/project.tsx"),\
          route(":pid/edit", "./projects/edit-project.tsx"),\
        ]),\
      ]),\
    ] satisfies RouteConfig;
    

[](#dynamic-segments)
Dynamic Segments
--------------------------------------

If a path segment starts with `:` then it becomes a "dynamic segment". When the route matches the URL, the dynamic segment will be parsed from the URL and provided as `params` to other router APIs.

    route("teams/:teamId", "./team.tsx"),
    

    import type { Route } from "./+types/team";
    
    export async function loader({ params }: Route.LoaderArgs) {
      //                           ^? { teamId: string }
    }
    
    export default function Component({
      params,
    }: Route.ComponentProps) {
      params.teamId;
      //        ^ string
    }
    

You can have multiple dynamic segments in one route path:

    route("c/:categoryId/p/:productId", "./product.tsx"),
    

    import type { Route } from "./+types/product";
    
    async function loader({ params }: LoaderArgs) {
      //                    ^? { categoryId: string; productId: string }
    }
    

[](#optional-segments)
Optional Segments
----------------------------------------

You can make a route segment optional by adding a `?` to the end of the segment.

    route(":lang?/categories", "./categories.tsx"),
    

You can have optional static segments, too:

    route("users/:userId/edit?", "./user.tsx");
    

[](#splats)
Splats
------------------

Also known as "catchall" and "star" segments. If a route path pattern ends with `/*` then it will match any characters following the `/`, including other `/` characters.

    route("files/*", "./files.tsx"),
    

    export async function loader({ params }: Route.LoaderArgs) {
      // params["*"] will contain the remaining URL after files/
    }
    

You can destructure the `*`, you just have to assign it a new name. A common name is `splat`:

    const { "*": splat } = params;
    

[](#component-routes)
Component Routes
--------------------------------------

You can also use components that match the URL to elements anywhere in the component tree:

    import { Routes, Route } from "react-router";
    
    function Wizard() {
      return (
        <div>
          <h1>Some Wizard with Steps</h1>
          <Routes>
            <Route index element={<StepOne />} />
            <Route path="step-2" element={<StepTwo />} />
            <Route path="step-3" element={<StepThree />} />
          </Routes>
        </div>
      );
    }
    

Note that these routes do not participate in data loading, actions, code splitting, or any other route module features, so their use cases are more limited than those of the route module.

* * *

Next: [Route Module](./route-module)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/routing.md)

---

# Route Module  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/route-module)
[dev](/dev/start/framework/route-module)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Route Module

On this page

*   [Introduction](/start/framework/route-module#introduction)
    
*   [Component (`default`)](/start/framework/route-module#component-default)
    
*   [Props passed to the Component](/start/framework/route-module#props-passed-to-the-component)
    
*   [Using props](/start/framework/route-module#using-props)
    
*   [`loader`](/start/framework/route-module#loader)
    
*   [`clientLoader`](/start/framework/route-module#clientloader)
    
*   [`action`](/start/framework/route-module#action)
    
*   [`clientAction`](/start/framework/route-module#clientaction)
    
*   [`ErrorBoundary`](/start/framework/route-module#errorboundary)
    
*   [`HydrateFallback`](/start/framework/route-module#hydratefallback)
    
*   [`headers`](/start/framework/route-module#headers)
    
*   [`handle`](/start/framework/route-module#handle)
    
*   [`links`](/start/framework/route-module#links)
    
*   [`meta`](/start/framework/route-module#meta)
    
*   [`shouldRevalidate`](/start/framework/route-module#shouldrevalidate)
    

*   [Introduction](/start/framework/route-module#introduction)
    
*   [Component (`default`)](/start/framework/route-module#component-default)
    
*   [Props passed to the Component](/start/framework/route-module#props-passed-to-the-component)
    
*   [Using props](/start/framework/route-module#using-props)
    
*   [`loader`](/start/framework/route-module#loader)
    
*   [`clientLoader`](/start/framework/route-module#clientloader)
    
*   [`action`](/start/framework/route-module#action)
    
*   [`clientAction`](/start/framework/route-module#clientaction)
    
*   [`ErrorBoundary`](/start/framework/route-module#errorboundary)
    
*   [`HydrateFallback`](/start/framework/route-module#hydratefallback)
    
*   [`headers`](/start/framework/route-module#headers)
    
*   [`handle`](/start/framework/route-module#handle)
    
*   [`links`](/start/framework/route-module#links)
    
*   [`meta`](/start/framework/route-module#meta)
    
*   [`shouldRevalidate`](/start/framework/route-module#shouldrevalidate)
    

[](#route-module)
Route Module
==============================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

The files referenced in `routes.ts` are called Route Modules.

    route("teams/:teamId", "./team.tsx"),
    //           route module ^^^^^^^^
    

Route modules are the foundation of React Router's framework features, they define:

*   automatic code-splitting
*   data loading
*   actions
*   revalidation
*   error boundaries
*   and more

This guide is a quick overview of every route module feature. The rest of the getting started guides will cover these features in more detail.

[](#component-default)
Component (`default`)
--------------------------------------------

The `default` export in a route module defines the component that will render when the route matches.

    export default function MyRouteComponent() {
      return (
        <div>
          <h1>Look ma!</h1>
          <p>
            I'm still using React Router after like 10 years.
          </p>
        </div>
      );
    }
    

### [](#props-passed-to-the-component)
Props passed to the Component

When the component is rendered, it is provided the props defined in `Route.ComponentProps` that React Router will automatically generate for you. These props include:

1.  `loaderData`: The data returned from the `loader` function in this route module
2.  `actionData`: The data returned from the `action` function in this route module
3.  `params`: An object containing the route parameters (if any).
4.  `matches`: An array of all the matches in the current route tree.

You can use these props in place of hooks like `useLoaderData` or `useParams`. This may be preferrable because they will be automatically typed correctly for the route.

### [](#using-props)
Using props

    import type { Route } from "./+types/route-name";
    
    export default function MyRouteComponent({
      loaderData,
      actionData,
      params,
      matches,
    }: Route.ComponentProps) {
      return (
        <div>
          <h1>Welcome to My Route with Props!</h1>
          <p>Loader Data: {JSON.stringify(loaderData)}</p>
          <p>Action Data: {JSON.stringify(actionData)}</p>
          <p>Route Parameters: {JSON.stringify(params)}</p>
          <p>Matched Routes: {JSON.stringify(matches)}</p>
        </div>
      );
    }
    

[](#loader)
`loader`
--------------------

Route loaders provide data to route components before they are rendered. They are only called on the server when server rendering or during the build with pre-rendering.

    export async function loader() {
      return { message: "Hello, world!" };
    }
    
    export default function MyRoute({ loaderData }) {
      return <h1>{loaderData.message}</h1>;
    }
    

See also:

*   [`loader` params](https://api.reactrouter.com/v7/interfaces/react_router.LoaderFunctionArgs)
    

[](#clientloader)
`clientLoader`
--------------------------------

Called only in the browser, route client loaders provide data to route components in addition to, or in place of, route loaders.

    export async function clientLoader({ serverLoader }) {
      // call the server loader
      const serverData = await serverLoader();
      // And/or fetch data on the client
      const data = getDataFromClient();
      // Return the data to expose through useLoaderData()
      return data;
    }
    

Client loaders can participate in initial page load hydration of server rendered pages by setting the `hydrate` property on the function:

    export async function clientLoader() {
      // ...
    }
    clientLoader.hydrate = true as const;
    

By using `as const`, TypeScript will infer that the type for `clientLoader.hydrate` is `true` instead of `boolean`. That way, React Router can derive types for `loaderData` based on the value of `clientLoader.hydrate`.

See also:

*   [`clientLoader` params](https://api.reactrouter.com/v7/types/react_router.ClientLoaderFunctionArgs)
    

[](#action)
`action`
--------------------

Route actions allow server-side data mutations with automatic revalidation of all loader data on the page when called from `<Form>`, `useFetcher`, and `useSubmit`.

    // route("/list", "./list.tsx")
    import { Form } from "react-router";
    import { TodoList } from "~/components/TodoList";
    
    // this data will be loaded after the action completes...
    export async function loader() {
      const items = await fakeDb.getItems();
      return { items };
    }
    
    // ...so that the list here is updated automatically
    export default function Items({ loaderData }) {
      return (
        <div>
          <List items={loaderData.items} />
          <Form method="post" navigate={false} action="/list">
            <input type="text" name="title" />
            <button type="submit">Create Todo</button>
          </Form>
        </div>
      );
    }
    
    export async function action({ request }) {
      const data = await request.formData();
      const todo = await fakeDb.addItem({
        title: data.get("title"),
      });
      return { ok: true };
    }
    

[](#clientaction)
`clientAction`
--------------------------------

Like route actions but only called in the browser.

    export async function clientAction({ serverAction }) {
      fakeInvalidateClientSideCache();
      // can still call the server action if needed
      const data = await serverAction();
      return data;
    }
    

See also:

*   [`clientAction` params](https://api.reactrouter.com/v7/types/react_router.ClientActionFunctionArgs)
    

[](#errorboundary)
`ErrorBoundary`
----------------------------------

When other route module APIs throw, the route module `ErrorBoundary` will render instead of the route component.

    import {
      isRouteErrorResponse,
      useRouteError,
    } from "react-router";
    
    export function ErrorBoundary() {
      const error = useRouteError();
    
      if (isRouteErrorResponse(error)) {
        return (
          <div>
            <h1>
              {error.status} {error.statusText}
            </h1>
            <p>{error.data}</p>
          </div>
        );
      } else if (error instanceof Error) {
        return (
          <div>
            <h1>Error</h1>
            <p>{error.message}</p>
            <p>The stack trace is:</p>
            <pre>{error.stack}</pre>
          </div>
        );
      } else {
        return <h1>Unknown Error</h1>;
      }
    }
    

[](#hydratefallback)
`HydrateFallback`
--------------------------------------

On initial page load, the route component renders only after the client loader is finished. If exported, a `HydrateFallback` can render immediately in place of the route component.

    export async function clientLoader() {
      const data = await fakeLoadLocalGameData();
      return data;
    }
    
    export function HydrateFallback() {
      return <p>Loading Game...</p>;
    }
    
    export default function Component({ loaderData }) {
      return <Game data={loaderData} />;
    }
    

[](#headers)
`headers`
----------------------

Route headers define HTTP headers to be sent with the response when server rendering.

    export function headers() {
      return {
        "X-Stretchy-Pants": "its for fun",
        "Cache-Control": "max-age=300, s-maxage=3600",
      };
    }
    

[](#handle)
`handle`
--------------------

Route handle allows apps to add anything to a route match in `useMatches` to create abstractions (like breadcrumbs, etc.).

    export const handle = {
      its: "all yours",
    };
    

[](#links)
`links`
------------------

Route links define [`<link>` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link)
s to be rendered in the document `<head>`.

    export function links() {
      return [\
        {\
          rel: "icon",\
          href: "/favicon.png",\
          type: "image/png",\
        },\
        {\
          rel: "stylesheet",\
          href: "https://example.com/some/styles.css",\
        },\
        {\
          rel: "preload",\
          href: "/images/banner.jpg",\
          as: "image",\
        },\
      ];
    }
    

All routes links will be aggregated and rendered through the `<Links />` component, usually rendered in your app root:

    import { Links } from "react-router";
    
    export default function Root() {
      return (
        <html>
          <head>
            <Links />
          </head>
    
          <body />
        </html>
      );
    }
    

[](#meta)
`meta`
----------------

Route meta defines meta tags to be rendered in the `<head>` of the document.

    export function meta() {
      return [\
        { title: "Very cool app" },\
        {\
          property: "og:title",\
          content: "Very cool app",\
        },\
        {\
          name: "description",\
          content: "This app is the best",\
        },\
      ];
    }
    

All routes' meta will be aggregated and rendered through the `<Meta />` component, usually rendered in your app root:

    import { Meta } from "react-router";
    
    export default function Root() {
      return (
        <html>
          <head>
            <Meta />
          </head>
    
          <body />
        </html>
      );
    }
    

**See also**

*   [`meta` params](https://api.reactrouter.com/v7/interfaces/react_router.MetaArgs)
    

[](#shouldrevalidate)
`shouldRevalidate`
----------------------------------------

In framework mode, route loaders are automatically revalidated after all navigations and form submissions (this is different from [Data Mode](../data/route-object#shouldrevalidate)
). This enables middleware and loaders to share a request context and optimize in different ways than then they would be in Data Mode.

Defining this function allows you to opt out of revalidation for a route loader for navigations and form submissions.

    import type { ShouldRevalidateFunctionArgs } from "react-router";
    
    export function shouldRevalidate(
      arg: ShouldRevalidateFunctionArgs
    ) {
      return true;
    }
    

[`ShouldRevalidateFunctionArgs` Reference Documentation ↗](https://api.reactrouter.com/v7/interfaces/react_router.ShouldRevalidateFunctionArgs.html)

* * *

Next: [Rendering Strategies](./rendering)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/route-module.md)

---

# Data Loading  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/data-loading)
[dev](/dev/start/framework/data-loading)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Data Loading

On this page

*   [Introduction](/start/framework/data-loading#introduction)
    
*   [Client Data Loading](/start/framework/data-loading#client-data-loading)
    
*   [Server Data Loading](/start/framework/data-loading#server-data-loading)
    
*   [Static Data Loading](/start/framework/data-loading#static-data-loading)
    
*   [Using Both Loaders](/start/framework/data-loading#using-both-loaders)
    

*   [Introduction](/start/framework/data-loading#introduction)
    
*   [Client Data Loading](/start/framework/data-loading#client-data-loading)
    
*   [Server Data Loading](/start/framework/data-loading#server-data-loading)
    
*   [Static Data Loading](/start/framework/data-loading#static-data-loading)
    
*   [Using Both Loaders](/start/framework/data-loading#using-both-loaders)
    

[](#data-loading)
Data Loading
==============================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

Data is provided to the route component from `loader` and `clientLoader`.

Loader data is automatically serialized from loaders and deserialized in components. In addition to primitive values like strings and numbers, loaders can return promises, maps, sets, dates and more.

The type for the `loaderData` prop is [automatically generated](../../explanation/type-safety)
.

[](#client-data-loading)
Client Data Loading
--------------------------------------------

`clientLoader` is used to fetch data on the client. This is useful for pages or full projects that you'd prefer to fetch data from the browser only.

    // route("products/:pid", "./product.tsx");
    import type { Route } from "./+types/product";
    
    export async function clientLoader({
      params,
    }: Route.ClientLoaderArgs) {
      const res = await fetch(`/api/products/${params.pid}`);
      const product = await res.json();
      return product;
    }
    
    // HydrateFallback is rendered while the client loader is running
    export function HydrateFallback() {
      return <div>Loading...</div>;
    }
    
    export default function Product({
      loaderData,
    }: Route.ComponentProps) {
      const { name, description } = loaderData;
      return (
        <div>
          <h1>{name}</h1>
          <p>{description}</p>
        </div>
      );
    }
    

[](#server-data-loading)
Server Data Loading
--------------------------------------------

When server rendering, `loader` is used for both initial page loads and client navigations. Client navigations call the loader through an automatic `fetch` by React Router from the browser to your server.

    // route("products/:pid", "./product.tsx");
    import type { Route } from "./+types/product";
    import { fakeDb } from "../db";
    
    export async function loader({ params }: Route.LoaderArgs) {
      const product = await fakeDb.getProduct(params.pid);
      return product;
    }
    
    export default function Product({
      loaderData,
    }: Route.ComponentProps) {
      const { name, description } = loaderData;
      return (
        <div>
          <h1>{name}</h1>
          <p>{description}</p>
        </div>
      );
    }
    

Note that the `loader` function is removed from client bundles so you can use server only APIs without worrying about them being included in the browser.

[](#static-data-loading)
Static Data Loading
--------------------------------------------

When pre-rendering, loaders are used to fetch data during the production build.

    // route("products/:pid", "./product.tsx");
    import type { Route } from "./+types/product";
    
    export async function loader({ params }: Route.LoaderArgs) {
      let product = await getProductFromCSVFile(params.pid);
      return product;
    }
    
    export default function Product({
      loaderData,
    }: Route.ComponentProps) {
      const { name, description } = loaderData;
      return (
        <div>
          <h1>{name}</h1>
          <p>{description}</p>
        </div>
      );
    }
    

The URLs to pre-render are specified in react-router.config.ts:

    import type { Config } from "@react-router/dev/config";
    
    export default {
      async prerender() {
        let products = await readProductsFromCSVFile();
        return products.map(
          (product) => `/products/${product.id}`
        );
      },
    } satisfies Config;
    

Note that when server rendering, any URLs that aren't pre-rendered will be server rendered as usual, allowing you to pre-render some data at a single route while still server rendering the rest.

[](#using-both-loaders)
Using Both Loaders
------------------------------------------

`loader` and `clientLoader` can be used together. The `loader` will be used on the server for initial SSR (or pre-rendering) and the `clientLoader` will be used on subsequent client-side navigations.

    // route("products/:pid", "./product.tsx");
    import type { Route } from "./+types/product";
    import { fakeDb } from "../db";
    
    export async function loader({ params }: Route.LoaderArgs) {
      return fakeDb.getProduct(params.pid);
    }
    
    export async function clientLoader({
      serverLoader,
      params,
    }: Route.ClientLoaderArgs) {
      const res = await fetch(`/api/products/${params.pid}`);
      const serverData = await serverLoader();
      return { ...serverData, ...res.json() };
    }
    
    export default function Product({
      loaderData,
    }: Route.ComponentProps) {
      const { name, description } = loaderData;
    
      return (
        <div>
          <h1>{name}</h1>
          <p>{description}</p>
        </div>
      );
    }
    

You can also force the client loader to run during hydration and before the page renders by setting the `hydrate` property on the function. In this situation you will want to render a `HydrateFallback` component to show a fallback UI while the client loader runs.

    export async function loader() {
      /* ... */
    }
    
    export async function clientLoader() {
      /* ... */
    }
    
    // force the client loader to run during hydration
    clientLoader.hydrate = true as const; // `as const` for type inference
    
    export function HydrateFallback() {
      return <div>Loading...</div>;
    }
    
    export default function Product() {
      /* ... */
    }
    

* * *

Next: [Actions](./actions)

See also:

*   [Streaming with Suspense](../../how-to/suspense)
    
*   [Client Data](../../how-to/client-data)
    
*   [Using Fetchers](../../how-to/fetchers#loading-data)
    

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/data-loading.md)

---

# Rendering Strategies  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/rendering)
[dev](/dev/start/framework/rendering)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Rendering Strategies

On this page

*   [Introduction](/start/framework/rendering#introduction)
    
*   [Client Side Rendering](/start/framework/rendering#client-side-rendering)
    
*   [Server Side Rendering](/start/framework/rendering#server-side-rendering)
    
*   [Static Pre-rendering](/start/framework/rendering#static-pre-rendering)
    

*   [Introduction](/start/framework/rendering#introduction)
    
*   [Client Side Rendering](/start/framework/rendering#client-side-rendering)
    
*   [Server Side Rendering](/start/framework/rendering#server-side-rendering)
    
*   [Static Pre-rendering](/start/framework/rendering#static-pre-rendering)
    

[](#rendering-strategies)
Rendering Strategies
==============================================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

There are three rendering strategies in React Router:

*   Client Side Rendering
*   Server Side Rendering
*   Static Pre-rendering

[](#client-side-rendering)
Client Side Rendering
------------------------------------------------

Routes are always client side rendered as the user navigates around the app. If you're looking to build a Single Page App, disable server rendering:

    import type { Config } from "@react-router/dev/config";
    
    export default {
      ssr: false,
    } satisfies Config;
    

[](#server-side-rendering)
Server Side Rendering
------------------------------------------------

    import type { Config } from "@react-router/dev/config";
    
    export default {
      ssr: true,
    } satisfies Config;
    

Server side rendering requires a deployment that supports it. Though it's a global setting, individual routes can still be statically pre-rendered. Routes can also use client data loading with `clientLoader` to avoid server rendering/fetching for their portion of the UI.

[](#static-pre-rendering)
Static Pre-rendering
----------------------------------------------

    import type { Config } from "@react-router/dev/config";
    
    export default {
      // return a list of URLs to prerender at build time
      async prerender() {
        return ["/", "/about", "/contact"];
      },
    } satisfies Config;
    

Pre-rendering is a build-time operation that generates static HTML and client navigation data payloads for a list of URLs. This is useful for SEO and performance, especially for deployments without server rendering. When pre-rendering, route module loaders are used to fetch data at build time.

* * *

Next: [Data Loading](./data-loading)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/rendering.md)

---

# Actions  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/actions)
[dev](/dev/start/framework/actions)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Actions

On this page

*   [Introduction](/start/framework/actions#introduction)
    
*   [Client Actions](/start/framework/actions#client-actions)
    
*   [Server Actions](/start/framework/actions#server-actions)
    
*   [Calling Actions](/start/framework/actions#calling-actions)
    
*   [Calling actions with a Form](/start/framework/actions#calling-actions-with-a-form)
    
*   [Calling actions with useSubmit](/start/framework/actions#calling-actions-with-usesubmit)
    
*   [Calling actions with a fetcher](/start/framework/actions#calling-actions-with-a-fetcher)
    

*   [Introduction](/start/framework/actions#introduction)
    
*   [Client Actions](/start/framework/actions#client-actions)
    
*   [Server Actions](/start/framework/actions#server-actions)
    
*   [Calling Actions](/start/framework/actions#calling-actions)
    
*   [Calling actions with a Form](/start/framework/actions#calling-actions-with-a-form)
    
*   [Calling actions with useSubmit](/start/framework/actions#calling-actions-with-usesubmit)
    
*   [Calling actions with a fetcher](/start/framework/actions#calling-actions-with-a-fetcher)
    

[](#actions)
Actions
====================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

Data mutations are done through Route actions. When the action completes, all loader data on the page is revalidated to keep your UI in sync with the data without writing any code to do it.

Route actions defined with `action` are only called on the server while actions defined with `clientAction` are run in the browser.

[](#client-actions)
Client Actions
----------------------------------

Client actions only run in the browser and take priority over a server action when both are defined.

    // route('/projects/:projectId', './project.tsx')
    import type { Route } from "./+types/project";
    import { Form } from "react-router";
    import { someApi } from "./api";
    
    export async function clientAction({
      request,
    }: Route.ClientActionArgs) {
      let formData = await request.formData();
      let title = formData.get("title");
      let project = await someApi.updateProject({ title });
      return project;
    }
    
    export default function Project({
      actionData,
    }: Route.ComponentProps) {
      return (
        <div>
          <h1>Project</h1>
          <Form method="post">
            <input type="text" name="title" />
            <button type="submit">Submit</button>
          </Form>
          {actionData ? (
            <p>{actionData.title} updated</p>
          ) : null}
        </div>
      );
    }
    

[](#server-actions)
Server Actions
----------------------------------

Server actions only run on the server and are removed from client bundles.

    // route('/projects/:projectId', './project.tsx')
    import type { Route } from "./+types/project";
    import { Form } from "react-router";
    import { fakeDb } from "../db";
    
    export async function action({
      request,
    }: Route.ActionArgs) {
      let formData = await request.formData();
      let title = formData.get("title");
      let project = await fakeDb.updateProject({ title });
      return project;
    }
    
    export default function Project({
      actionData,
    }: Route.ComponentProps) {
      return (
        <div>
          <h1>Project</h1>
          <Form method="post">
            <input type="text" name="title" />
            <button type="submit">Submit</button>
          </Form>
          {actionData ? (
            <p>{actionData.title} updated</p>
          ) : null}
        </div>
      );
    }
    

[](#calling-actions)
Calling Actions
------------------------------------

Actions are called declaratively through `<Form>` and imperatively through `useSubmit` (or `<fetcher.Form>` and `fetcher.submit`) by referencing the route's path and a "post" method.

### [](#calling-actions-with-a-form)
Calling actions with a Form

    import { Form } from "react-router";
    
    function SomeComponent() {
      return (
        <Form action="/projects/123" method="post">
          <input type="text" name="title" />
          <button type="submit">Submit</button>
        </Form>
      );
    }
    

This will cause a navigation and a new entry will be added to the browser history.

### [](#calling-actions-with-usesubmit)
Calling actions with useSubmit

You can submit form data to an action imperatively with `useSubmit`.

    import { useCallback } from "react";
    import { useSubmit } from "react-router";
    import { useFakeTimer } from "fake-lib";
    
    function useQuizTimer() {
      let submit = useSubmit();
    
      let cb = useCallback(() => {
        submit(
          { quizTimedOut: true },
          { action: "/end-quiz", method: "post" }
        );
      }, []);
    
      let tenMinutes = 10 * 60 * 1000;
      useFakeTimer(tenMinutes, cb);
    }
    

This will cause a navigation and a new entry will be added to the browser history.

### [](#calling-actions-with-a-fetcher)
Calling actions with a fetcher

Fetchers allow you to submit data to actions (and loaders) without causing a navigation (no new entries in the browser history).

    import { useFetcher } from "react-router";
    
    function Task() {
      let fetcher = useFetcher();
      let busy = fetcher.state !== "idle";
    
      return (
        <fetcher.Form method="post" action="/update-task/123">
          <input type="text" name="title" />
          <button type="submit">
            {busy ? "Saving..." : "Save"}
          </button>
        </fetcher.Form>
      );
    }
    

They also have the imperative `submit` method.

    fetcher.submit(
      { title: "New Title" },
      { action: "/update-task/123", method: "post" }
    );
    

See the [Using Fetchers](../../how-to/fetchers)
 guide for more information.

* * *

Next: [Navigating](./navigating)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/actions.md)

---

# CHANGELOG.md  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/home)
[dev](/dev/)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

CHANGELOG.md

On this page

*   [v7.6.0](/changelog#v760)
    
*   [What's Changed](/changelog#whats-changed)
    
*   [Minor Changes](/changelog#minor-changes)
    
*   [Patch Changes](/changelog#patch-changes)
    
*   [Unstable Changes](/changelog#unstable-changes)
    
*   [Changes by Package](/changelog#changes-by-package)
    
*   [v7.5.3](/changelog#v753)
    
*   [Patch Changes](/changelog#patch-changes-1)
    
*   [v7.5.2](/changelog#v752)
    
*   [Security Notice](/changelog#security-notice)
    
*   [Patch Changes](/changelog#patch-changes-2)
    
*   [v7.5.1](/changelog#v751)
    
*   [Patch Changes](/changelog#patch-changes-3)
    
*   [Unstable Changes](/changelog#unstable-changes-1)
    
*   [v7.5.0](/changelog#v750)
    
*   [What's Changed](/changelog#whats-changed-1)
    
*   [Minor Changes](/changelog#minor-changes-1)
    
*   [Patch Changes](/changelog#patch-changes-4)
    
*   [Unstable Changes](/changelog#unstable-changes-2)
    
*   [Changes by Package](/changelog#changes-by-package-1)
    
*   [v7.4.1](/changelog#v741)
    
*   [Security Notice](/changelog#security-notice-1)
    
*   [Patch Changes](/changelog#patch-changes-5)
    
*   [Unstable Changes](/changelog#unstable-changes-3)
    
*   [v7.4.0](/changelog#v740)
    
*   [Minor Changes](/changelog#minor-changes-2)
    
*   [Patch Changes](/changelog#patch-changes-6)
    
*   [Unstable Changes](/changelog#unstable-changes-4)
    
*   [Changes by Package](/changelog#changes-by-package-2)
    
*   [v7.3.0](/changelog#v730)
    
*   [Minor Changes](/changelog#minor-changes-3)
    
*   [Patch Changes](/changelog#patch-changes-7)
    
*   [Unstable Changes](/changelog#unstable-changes-5)
    
*   [Changes by Package](/changelog#changes-by-package-3)
    
*   [v7.2.0](/changelog#v720)
    
*   [What's Changed](/changelog#whats-changed-2)
    
*   [Minor Changes](/changelog#minor-changes-4)
    
*   [Patch Changes](/changelog#patch-changes-8)
    
*   [Unstable Changes](/changelog#unstable-changes-6)
    
*   [Changes by Package](/changelog#changes-by-package-4)
    
*   [v7.1.5](/changelog#v715)
    
*   [Patch Changes](/changelog#patch-changes-9)
    
*   [v7.1.4](/changelog#v714)
    
*   [Patch Changes](/changelog#patch-changes-10)
    
*   [v7.1.3](/changelog#v713)
    
*   [Patch Changes](/changelog#patch-changes-11)
    
*   [v7.1.2](/changelog#v712)
    
*   [Patch Changes](/changelog#patch-changes-12)
    
*   [v7.1.1](/changelog#v711)
    
*   [Patch Changes](/changelog#patch-changes-13)
    
*   [v7.1.0](/changelog#v710)
    
*   [Minor Changes](/changelog#minor-changes-5)
    
*   [Patch Changes](/changelog#patch-changes-14)
    
*   [Changes by Package](/changelog#changes-by-package-5)
    
*   [v7.0.2](/changelog#v702)
    
*   [Patch Changes](/changelog#patch-changes-15)
    
*   [v7.0.1](/changelog#v701)
    
*   [Patch Changes](/changelog#patch-changes-16)
    
*   [v7.0.0](/changelog#v700)
    
*   [Breaking Changes](/changelog#breaking-changes)
    
*   [Other Notable Changes](/changelog#other-notable-changes)
    
*   [Major Changes (`react-router`)](/changelog#major-changes-react-router)
    
*   [Major Changes (`@react-router/*`)](/changelog#major-changes-react-router-1)
    
*   [Minor Changes](/changelog#minor-changes-6)
    
*   [Patch Changes](/changelog#patch-changes-17)
    
*   [Changes by Package](/changelog#changes-by-package-6)
    
*   [v6.30.0](/changelog#v6300)
    
*   [Minor Changes](/changelog#minor-changes-7)
    
*   [Patch Changes](/changelog#patch-changes-18)
    
*   [v6.29.0](/changelog#v6290)
    
*   [Minor Changes](/changelog#minor-changes-8)
    
*   [Patch Changes](/changelog#patch-changes-19)
    
*   [v6.28.2](/changelog#v6282)
    
*   [Patch Changes](/changelog#patch-changes-20)
    
*   [v6.28.1](/changelog#v6281)
    
*   [Patch Changes](/changelog#patch-changes-21)
    
*   [v6.28.0](/changelog#v6280)
    
*   [What's Changed](/changelog#whats-changed-3)
    
*   [Minor Changes](/changelog#minor-changes-9)
    
*   [Patch Changes](/changelog#patch-changes-22)
    
*   [v6.27.0](/changelog#v6270)
    
*   [What's Changed](/changelog#whats-changed-4)
    
*   [Minor Changes](/changelog#minor-changes-10)
    
*   [Patch Changes](/changelog#patch-changes-23)
    
*   [v6.26.2](/changelog#v6262)
    
*   [Patch Changes](/changelog#patch-changes-24)
    
*   [v6.26.1](/changelog#v6261)
    
*   [Patch Changes](/changelog#patch-changes-25)
    
*   [v6.26.0](/changelog#v6260)
    
*   [Minor Changes](/changelog#minor-changes-11)
    
*   [Patch Changes](/changelog#patch-changes-26)
    
*   [v6.25.1](/changelog#v6251)
    
*   [Patch Changes](/changelog#patch-changes-27)
    
*   [v6.25.0](/changelog#v6250)
    
*   [What's Changed](/changelog#whats-changed-5)
    
*   [Minor Changes](/changelog#minor-changes-12)
    
*   [Patch Changes](/changelog#patch-changes-28)
    
*   [v6.24.1](/changelog#v6241)
    
*   [Patch Changes](/changelog#patch-changes-29)
    
*   [v6.24.0](/changelog#v6240)
    
*   [What's Changed](/changelog#whats-changed-6)
    
*   [Minor Changes](/changelog#minor-changes-13)
    
*   [Patch Changes](/changelog#patch-changes-30)
    
*   [v6.23.1](/changelog#v6231)
    
*   [Patch Changes](/changelog#patch-changes-31)
    
*   [v6.23.0](/changelog#v6230)
    
*   [What's Changed](/changelog#whats-changed-7)
    
*   [Minor Changes](/changelog#minor-changes-14)
    
*   [v6.22.3](/changelog#v6223)
    
*   [Patch Changes](/changelog#patch-changes-32)
    
*   [v6.22.2](/changelog#v6222)
    
*   [Patch Changes](/changelog#patch-changes-33)
    
*   [v6.22.1](/changelog#v6221)
    
*   [Patch Changes](/changelog#patch-changes-34)
    
*   [v6.22.0](/changelog#v6220)
    
*   [What's Changed](/changelog#whats-changed-8)
    
*   [Minor Changes](/changelog#minor-changes-15)
    
*   [Patch Changes](/changelog#patch-changes-35)
    
*   [v6.21.3](/changelog#v6213)
    
*   [Patch Changes](/changelog#patch-changes-36)
    
*   [v6.21.2](/changelog#v6212)
    
*   [Patch Changes](/changelog#patch-changes-37)
    
*   [v6.21.1](/changelog#v6211)
    
*   [Patch Changes](/changelog#patch-changes-38)
    
*   [v6.21.0](/changelog#v6210)
    
*   [What's Changed](/changelog#whats-changed-9)
    
*   [Minor Changes](/changelog#minor-changes-16)
    
*   [Patch Changes](/changelog#patch-changes-39)
    
*   [v6.20.1](/changelog#v6201)
    
*   [Patch Changes](/changelog#patch-changes-40)
    
*   [v6.20.0](/changelog#v6200)
    
*   [Minor Changes](/changelog#minor-changes-17)
    
*   [Patch Changes](/changelog#patch-changes-41)
    
*   [v6.19.0](/changelog#v6190)
    
*   [What's Changed](/changelog#whats-changed-10)
    
*   [Minor Changes](/changelog#minor-changes-18)
    
*   [Patch Changes](/changelog#patch-changes-42)
    
*   [v6.18.0](/changelog#v6180)
    
*   [What's Changed](/changelog#whats-changed-11)
    
*   [Minor Changes](/changelog#minor-changes-19)
    
*   [Patch Changes](/changelog#patch-changes-43)
    
*   [v6.17.0](/changelog#v6170)
    
*   [What's Changed](/changelog#whats-changed-12)
    
*   [Minor Changes](/changelog#minor-changes-20)
    
*   [Patch Changes](/changelog#patch-changes-44)
    
*   [v6.16.0](/changelog#v6160)
    
*   [Minor Changes](/changelog#minor-changes-21)
    
*   [Patch Changes](/changelog#patch-changes-45)
    
*   [v6.15.0](/changelog#v6150)
    
*   [Minor Changes](/changelog#minor-changes-22)
    
*   [Patch Changes](/changelog#patch-changes-46)
    
*   [v6.14.2](/changelog#v6142)
    
*   [Patch Changes](/changelog#patch-changes-47)
    
*   [v6.14.1](/changelog#v6141)
    
*   [Patch Changes](/changelog#patch-changes-48)
    
*   [v6.14.0](/changelog#v6140)
    
*   [What's Changed](/changelog#whats-changed-13)
    
*   [Minor Changes](/changelog#minor-changes-23)
    
*   [Patch Changes](/changelog#patch-changes-49)
    
*   [v6.13.0](/changelog#v6130)
    
*   [What's Changed](/changelog#whats-changed-14)
    
*   [Minor Changes](/changelog#minor-changes-24)
    
*   [Patch Changes](/changelog#patch-changes-50)
    
*   [v6.12.1](/changelog#v6121)
    
*   [Patch Changes](/changelog#patch-changes-51)
    
*   [v6.12.0](/changelog#v6120)
    
*   [What's Changed](/changelog#whats-changed-15)
    
*   [Minor Changes](/changelog#minor-changes-25)
    
*   [Patch Changes](/changelog#patch-changes-52)
    
*   [v6.11.2](/changelog#v6112)
    
*   [Patch Changes](/changelog#patch-changes-53)
    
*   [v6.11.1](/changelog#v6111)
    
*   [Patch Changes](/changelog#patch-changes-54)
    
*   [v6.11.0](/changelog#v6110)
    
*   [Minor Changes](/changelog#minor-changes-26)
    
*   [Patch Changes](/changelog#patch-changes-55)
    
*   [v6.10.0](/changelog#v6100)
    
*   [What's Changed](/changelog#whats-changed-16)
    
*   [Minor Changes](/changelog#minor-changes-27)
    
*   [Patch Changes](/changelog#patch-changes-56)
    
*   [v6.9.0](/changelog#v690)
    
*   [What's Changed](/changelog#whats-changed-17)
    
*   [Minor Changes](/changelog#minor-changes-28)
    
*   [Patch Changes](/changelog#patch-changes-57)
    
*   [v6.8.2](/changelog#v682)
    
*   [Patch Changes](/changelog#patch-changes-58)
    
*   [v6.8.1](/changelog#v681)
    
*   [Patch Changes](/changelog#patch-changes-59)
    
*   [v6.8.0](/changelog#v680)
    
*   [Minor Changes](/changelog#minor-changes-29)
    
*   [Patch Changes](/changelog#patch-changes-60)
    
*   [v6.7.0](/changelog#v670)
    
*   [Minor Changes](/changelog#minor-changes-30)
    
*   [Patch Changes](/changelog#patch-changes-61)
    
*   [v6.6.2](/changelog#v662)
    
*   [Patch Changes](/changelog#patch-changes-62)
    
*   [v6.6.1](/changelog#v661)
    
*   [Patch Changes](/changelog#patch-changes-63)
    
*   [v6.6.0](/changelog#v660)
    
*   [What's Changed](/changelog#whats-changed-18)
    
*   [Minor Changes](/changelog#minor-changes-31)
    
*   [Patch Changes](/changelog#patch-changes-64)
    
*   [v6.5.0](/changelog#v650)
    
*   [What's Changed](/changelog#whats-changed-19)
    
*   [Minor Changes](/changelog#minor-changes-32)
    
*   [Patch Changes](/changelog#patch-changes-65)
    
*   [v6.4.5](/changelog#v645)
    
*   [Patch Changes](/changelog#patch-changes-66)
    
*   [v6.4.4](/changelog#v644)
    
*   [Patch Changes](/changelog#patch-changes-67)
    
*   [v6.4.3](/changelog#v643)
    
*   [Patch Changes](/changelog#patch-changes-68)
    
*   [v6.4.2](/changelog#v642)
    
*   [Patch Changes](/changelog#patch-changes-69)
    
*   [v6.4.1](/changelog#v641)
    
*   [Patch Changes](/changelog#patch-changes-70)
    
*   [v6.4.0](/changelog#v640)
    
*   [What's Changed](/changelog#whats-changed-20)
    
*   [Patch Changes](/changelog#patch-changes-71)
    
*   [v6.3.0](/changelog#v630)
    
*   [Minor Changes](/changelog#minor-changes-33)
    
*   [v6.2.2](/changelog#v622)
    
*   [Patch Changes](/changelog#patch-changes-72)
    
*   [v6.2.1](/changelog#v621)
    
*   [Patch Changes](/changelog#patch-changes-73)
    
*   [v6.2.0](/changelog#v620)
    
*   [Minor Changes](/changelog#minor-changes-34)
    
*   [Patch Changes](/changelog#patch-changes-74)
    
*   [v6.1.1](/changelog#v611)
    
*   [Patch Changes](/changelog#patch-changes-75)
    
*   [v6.1.0](/changelog#v610)
    
*   [Minor Changes](/changelog#minor-changes-35)
    
*   [Patch Changes](/changelog#patch-changes-76)
    
*   [v6.0.2](/changelog#v602)
    
*   [Patch Changes](/changelog#patch-changes-77)
    
*   [v6.0.1](/changelog#v601)
    
*   [Patch Changes](/changelog#patch-changes-78)
    
*   [v6.0.0](/changelog#v600)
    

*   [v7.6.0](/changelog#v760)
    
*   [What's Changed](/changelog#whats-changed)
    
*   [Minor Changes](/changelog#minor-changes)
    
*   [Patch Changes](/changelog#patch-changes)
    
*   [Unstable Changes](/changelog#unstable-changes)
    
*   [Changes by Package](/changelog#changes-by-package)
    
*   [v7.5.3](/changelog#v753)
    
*   [Patch Changes](/changelog#patch-changes-1)
    
*   [v7.5.2](/changelog#v752)
    
*   [Security Notice](/changelog#security-notice)
    
*   [Patch Changes](/changelog#patch-changes-2)
    
*   [v7.5.1](/changelog#v751)
    
*   [Patch Changes](/changelog#patch-changes-3)
    
*   [Unstable Changes](/changelog#unstable-changes-1)
    
*   [v7.5.0](/changelog#v750)
    
*   [What's Changed](/changelog#whats-changed-1)
    
*   [Minor Changes](/changelog#minor-changes-1)
    
*   [Patch Changes](/changelog#patch-changes-4)
    
*   [Unstable Changes](/changelog#unstable-changes-2)
    
*   [Changes by Package](/changelog#changes-by-package-1)
    
*   [v7.4.1](/changelog#v741)
    
*   [Security Notice](/changelog#security-notice-1)
    
*   [Patch Changes](/changelog#patch-changes-5)
    
*   [Unstable Changes](/changelog#unstable-changes-3)
    
*   [v7.4.0](/changelog#v740)
    
*   [Minor Changes](/changelog#minor-changes-2)
    
*   [Patch Changes](/changelog#patch-changes-6)
    
*   [Unstable Changes](/changelog#unstable-changes-4)
    
*   [Changes by Package](/changelog#changes-by-package-2)
    
*   [v7.3.0](/changelog#v730)
    
*   [Minor Changes](/changelog#minor-changes-3)
    
*   [Patch Changes](/changelog#patch-changes-7)
    
*   [Unstable Changes](/changelog#unstable-changes-5)
    
*   [Changes by Package](/changelog#changes-by-package-3)
    
*   [v7.2.0](/changelog#v720)
    
*   [What's Changed](/changelog#whats-changed-2)
    
*   [Minor Changes](/changelog#minor-changes-4)
    
*   [Patch Changes](/changelog#patch-changes-8)
    
*   [Unstable Changes](/changelog#unstable-changes-6)
    
*   [Changes by Package](/changelog#changes-by-package-4)
    
*   [v7.1.5](/changelog#v715)
    
*   [Patch Changes](/changelog#patch-changes-9)
    
*   [v7.1.4](/changelog#v714)
    
*   [Patch Changes](/changelog#patch-changes-10)
    
*   [v7.1.3](/changelog#v713)
    
*   [Patch Changes](/changelog#patch-changes-11)
    
*   [v7.1.2](/changelog#v712)
    
*   [Patch Changes](/changelog#patch-changes-12)
    
*   [v7.1.1](/changelog#v711)
    
*   [Patch Changes](/changelog#patch-changes-13)
    
*   [v7.1.0](/changelog#v710)
    
*   [Minor Changes](/changelog#minor-changes-5)
    
*   [Patch Changes](/changelog#patch-changes-14)
    
*   [Changes by Package](/changelog#changes-by-package-5)
    
*   [v7.0.2](/changelog#v702)
    
*   [Patch Changes](/changelog#patch-changes-15)
    
*   [v7.0.1](/changelog#v701)
    
*   [Patch Changes](/changelog#patch-changes-16)
    
*   [v7.0.0](/changelog#v700)
    
*   [Breaking Changes](/changelog#breaking-changes)
    
*   [Other Notable Changes](/changelog#other-notable-changes)
    
*   [Major Changes (`react-router`)](/changelog#major-changes-react-router)
    
*   [Major Changes (`@react-router/*`)](/changelog#major-changes-react-router-1)
    
*   [Minor Changes](/changelog#minor-changes-6)
    
*   [Patch Changes](/changelog#patch-changes-17)
    
*   [Changes by Package](/changelog#changes-by-package-6)
    
*   [v6.30.0](/changelog#v6300)
    
*   [Minor Changes](/changelog#minor-changes-7)
    
*   [Patch Changes](/changelog#patch-changes-18)
    
*   [v6.29.0](/changelog#v6290)
    
*   [Minor Changes](/changelog#minor-changes-8)
    
*   [Patch Changes](/changelog#patch-changes-19)
    
*   [v6.28.2](/changelog#v6282)
    
*   [Patch Changes](/changelog#patch-changes-20)
    
*   [v6.28.1](/changelog#v6281)
    
*   [Patch Changes](/changelog#patch-changes-21)
    
*   [v6.28.0](/changelog#v6280)
    
*   [What's Changed](/changelog#whats-changed-3)
    
*   [Minor Changes](/changelog#minor-changes-9)
    
*   [Patch Changes](/changelog#patch-changes-22)
    
*   [v6.27.0](/changelog#v6270)
    
*   [What's Changed](/changelog#whats-changed-4)
    
*   [Minor Changes](/changelog#minor-changes-10)
    
*   [Patch Changes](/changelog#patch-changes-23)
    
*   [v6.26.2](/changelog#v6262)
    
*   [Patch Changes](/changelog#patch-changes-24)
    
*   [v6.26.1](/changelog#v6261)
    
*   [Patch Changes](/changelog#patch-changes-25)
    
*   [v6.26.0](/changelog#v6260)
    
*   [Minor Changes](/changelog#minor-changes-11)
    
*   [Patch Changes](/changelog#patch-changes-26)
    
*   [v6.25.1](/changelog#v6251)
    
*   [Patch Changes](/changelog#patch-changes-27)
    
*   [v6.25.0](/changelog#v6250)
    
*   [What's Changed](/changelog#whats-changed-5)
    
*   [Minor Changes](/changelog#minor-changes-12)
    
*   [Patch Changes](/changelog#patch-changes-28)
    
*   [v6.24.1](/changelog#v6241)
    
*   [Patch Changes](/changelog#patch-changes-29)
    
*   [v6.24.0](/changelog#v6240)
    
*   [What's Changed](/changelog#whats-changed-6)
    
*   [Minor Changes](/changelog#minor-changes-13)
    
*   [Patch Changes](/changelog#patch-changes-30)
    
*   [v6.23.1](/changelog#v6231)
    
*   [Patch Changes](/changelog#patch-changes-31)
    
*   [v6.23.0](/changelog#v6230)
    
*   [What's Changed](/changelog#whats-changed-7)
    
*   [Minor Changes](/changelog#minor-changes-14)
    
*   [v6.22.3](/changelog#v6223)
    
*   [Patch Changes](/changelog#patch-changes-32)
    
*   [v6.22.2](/changelog#v6222)
    
*   [Patch Changes](/changelog#patch-changes-33)
    
*   [v6.22.1](/changelog#v6221)
    
*   [Patch Changes](/changelog#patch-changes-34)
    
*   [v6.22.0](/changelog#v6220)
    
*   [What's Changed](/changelog#whats-changed-8)
    
*   [Minor Changes](/changelog#minor-changes-15)
    
*   [Patch Changes](/changelog#patch-changes-35)
    
*   [v6.21.3](/changelog#v6213)
    
*   [Patch Changes](/changelog#patch-changes-36)
    
*   [v6.21.2](/changelog#v6212)
    
*   [Patch Changes](/changelog#patch-changes-37)
    
*   [v6.21.1](/changelog#v6211)
    
*   [Patch Changes](/changelog#patch-changes-38)
    
*   [v6.21.0](/changelog#v6210)
    
*   [What's Changed](/changelog#whats-changed-9)
    
*   [Minor Changes](/changelog#minor-changes-16)
    
*   [Patch Changes](/changelog#patch-changes-39)
    
*   [v6.20.1](/changelog#v6201)
    
*   [Patch Changes](/changelog#patch-changes-40)
    
*   [v6.20.0](/changelog#v6200)
    
*   [Minor Changes](/changelog#minor-changes-17)
    
*   [Patch Changes](/changelog#patch-changes-41)
    
*   [v6.19.0](/changelog#v6190)
    
*   [What's Changed](/changelog#whats-changed-10)
    
*   [Minor Changes](/changelog#minor-changes-18)
    
*   [Patch Changes](/changelog#patch-changes-42)
    
*   [v6.18.0](/changelog#v6180)
    
*   [What's Changed](/changelog#whats-changed-11)
    
*   [Minor Changes](/changelog#minor-changes-19)
    
*   [Patch Changes](/changelog#patch-changes-43)
    
*   [v6.17.0](/changelog#v6170)
    
*   [What's Changed](/changelog#whats-changed-12)
    
*   [Minor Changes](/changelog#minor-changes-20)
    
*   [Patch Changes](/changelog#patch-changes-44)
    
*   [v6.16.0](/changelog#v6160)
    
*   [Minor Changes](/changelog#minor-changes-21)
    
*   [Patch Changes](/changelog#patch-changes-45)
    
*   [v6.15.0](/changelog#v6150)
    
*   [Minor Changes](/changelog#minor-changes-22)
    
*   [Patch Changes](/changelog#patch-changes-46)
    
*   [v6.14.2](/changelog#v6142)
    
*   [Patch Changes](/changelog#patch-changes-47)
    
*   [v6.14.1](/changelog#v6141)
    
*   [Patch Changes](/changelog#patch-changes-48)
    
*   [v6.14.0](/changelog#v6140)
    
*   [What's Changed](/changelog#whats-changed-13)
    
*   [Minor Changes](/changelog#minor-changes-23)
    
*   [Patch Changes](/changelog#patch-changes-49)
    
*   [v6.13.0](/changelog#v6130)
    
*   [What's Changed](/changelog#whats-changed-14)
    
*   [Minor Changes](/changelog#minor-changes-24)
    
*   [Patch Changes](/changelog#patch-changes-50)
    
*   [v6.12.1](/changelog#v6121)
    
*   [Patch Changes](/changelog#patch-changes-51)
    
*   [v6.12.0](/changelog#v6120)
    
*   [What's Changed](/changelog#whats-changed-15)
    
*   [Minor Changes](/changelog#minor-changes-25)
    
*   [Patch Changes](/changelog#patch-changes-52)
    
*   [v6.11.2](/changelog#v6112)
    
*   [Patch Changes](/changelog#patch-changes-53)
    
*   [v6.11.1](/changelog#v6111)
    
*   [Patch Changes](/changelog#patch-changes-54)
    
*   [v6.11.0](/changelog#v6110)
    
*   [Minor Changes](/changelog#minor-changes-26)
    
*   [Patch Changes](/changelog#patch-changes-55)
    
*   [v6.10.0](/changelog#v6100)
    
*   [What's Changed](/changelog#whats-changed-16)
    
*   [Minor Changes](/changelog#minor-changes-27)
    
*   [Patch Changes](/changelog#patch-changes-56)
    
*   [v6.9.0](/changelog#v690)
    
*   [What's Changed](/changelog#whats-changed-17)
    
*   [Minor Changes](/changelog#minor-changes-28)
    
*   [Patch Changes](/changelog#patch-changes-57)
    
*   [v6.8.2](/changelog#v682)
    
*   [Patch Changes](/changelog#patch-changes-58)
    
*   [v6.8.1](/changelog#v681)
    
*   [Patch Changes](/changelog#patch-changes-59)
    
*   [v6.8.0](/changelog#v680)
    
*   [Minor Changes](/changelog#minor-changes-29)
    
*   [Patch Changes](/changelog#patch-changes-60)
    
*   [v6.7.0](/changelog#v670)
    
*   [Minor Changes](/changelog#minor-changes-30)
    
*   [Patch Changes](/changelog#patch-changes-61)
    
*   [v6.6.2](/changelog#v662)
    
*   [Patch Changes](/changelog#patch-changes-62)
    
*   [v6.6.1](/changelog#v661)
    
*   [Patch Changes](/changelog#patch-changes-63)
    
*   [v6.6.0](/changelog#v660)
    
*   [What's Changed](/changelog#whats-changed-18)
    
*   [Minor Changes](/changelog#minor-changes-31)
    
*   [Patch Changes](/changelog#patch-changes-64)
    
*   [v6.5.0](/changelog#v650)
    
*   [What's Changed](/changelog#whats-changed-19)
    
*   [Minor Changes](/changelog#minor-changes-32)
    
*   [Patch Changes](/changelog#patch-changes-65)
    
*   [v6.4.5](/changelog#v645)
    
*   [Patch Changes](/changelog#patch-changes-66)
    
*   [v6.4.4](/changelog#v644)
    
*   [Patch Changes](/changelog#patch-changes-67)
    
*   [v6.4.3](/changelog#v643)
    
*   [Patch Changes](/changelog#patch-changes-68)
    
*   [v6.4.2](/changelog#v642)
    
*   [Patch Changes](/changelog#patch-changes-69)
    
*   [v6.4.1](/changelog#v641)
    
*   [Patch Changes](/changelog#patch-changes-70)
    
*   [v6.4.0](/changelog#v640)
    
*   [What's Changed](/changelog#whats-changed-20)
    
*   [Patch Changes](/changelog#patch-changes-71)
    
*   [v6.3.0](/changelog#v630)
    
*   [Minor Changes](/changelog#minor-changes-33)
    
*   [v6.2.2](/changelog#v622)
    
*   [Patch Changes](/changelog#patch-changes-72)
    
*   [v6.2.1](/changelog#v621)
    
*   [Patch Changes](/changelog#patch-changes-73)
    
*   [v6.2.0](/changelog#v620)
    
*   [Minor Changes](/changelog#minor-changes-34)
    
*   [Patch Changes](/changelog#patch-changes-74)
    
*   [v6.1.1](/changelog#v611)
    
*   [Patch Changes](/changelog#patch-changes-75)
    
*   [v6.1.0](/changelog#v610)
    
*   [Minor Changes](/changelog#minor-changes-35)
    
*   [Patch Changes](/changelog#patch-changes-76)
    
*   [v6.0.2](/changelog#v602)
    
*   [Patch Changes](/changelog#patch-changes-77)
    
*   [v6.0.1](/changelog#v601)
    
*   [Patch Changes](/changelog#patch-changes-78)
    
*   [v6.0.0](/changelog#v600)
    

[](#react-router-releases)
React Router Releases
================================================

This page lists all releases/release notes for React Router back to `v6.0.0`. For releases prior to v6, please refer to the [Github Releases Page](https://github.com/remix-run/react-router/releases)
.

We manage release notes in this file instead of the paginated Github Releases Page for 2 reasons:

*   Pagination in the Github UI means that you cannot easily search release notes for a large span of releases at once
*   The paginated Github interface also cuts off longer releases notes without indication in list view, and you need to click into the detail view to see the full set of release notes

Table of Contents

*   [React Router Releases](#react-router-releases)
    *   [v7.6.0](#v760)
        *   [What's Changed](#whats-changed)
            *   [`routeDiscovery` Config Option](#routediscovery-config-option)
                
            *   [Automatic Types for Future Flags](#automatic-types-for-future-flags)
                
        *   [Minor Changes](#minor-changes)
            
        *   [Patch Changes](#patch-changes)
            
        *   [Unstable Changes](#unstable-changes)
            
        *   [Changes by Package](#changes-by-package)
            
    *   [v7.5.3](#v753)
        *   [Patch Changes](#patch-changes-1)
            
    *   [v7.5.2](#v752)
        *   [Security Notice](#security-notice)
            
        *   [Patch Changes](#patch-changes-2)
            
    *   [v7.5.1](#v751)
        *   [Patch Changes](#patch-changes-3)
            
        *   [Unstable Changes](#unstable-changes-1)
            
    *   [v7.5.0](#v750)
        *   [What's Changed](#whats-changed-1)
            *   [`route.lazy` Object API](#routelazy-object-api)
                
        *   [Minor Changes](#minor-changes-1)
            
        *   [Patch Changes](#patch-changes-4)
            
        *   [Unstable Changes](#unstable-changes-2)
            
        *   [Changes by Package](#changes-by-package-1)
            
    *   [v7.4.1](#v741)
        *   [Security Notice](#security-notice-1)
            
        *   [Patch Changes](#patch-changes-5)
            
        *   [Unstable Changes](#unstable-changes-3)
            
    *   [v7.4.0](#v740)
        *   [Minor Changes](#minor-changes-2)
            
        *   [Patch Changes](#patch-changes-6)
            
        *   [Unstable Changes](#unstable-changes-4)
            
        *   [Changes by Package](#changes-by-package-2)
            
    *   [v7.3.0](#v730)
        *   [Minor Changes](#minor-changes-3)
            
        *   [Patch Changes](#patch-changes-7)
            
        *   [Unstable Changes](#unstable-changes-5)
            *   [Client-side `context` (unstable)](#client-side-context-unstable)
                
            *   [Middleware (unstable)](#middleware-unstable)
                *   [Middleware `context` parameter](#middleware-context-parameter)
                    
            *   [`unstable_SerializesTo`](#unstable_serializesto)
                
        *   [Changes by Package](#changes-by-package-3)
            
    *   [v7.2.0](#v720)
        *   [What's Changed](#whats-changed-2)
            *   [Type-safe `href` utility](#type-safe-href-utility)
                
            *   [Prerendering with a SPA Fallback](#prerendering-with-a-spa-fallback)
                
            *   [Allow a root `loader` in SPA Mode](#allow-a-root-loader-in-spa-mode)
                
        *   [Minor Changes](#minor-changes-4)
            
        *   [Patch Changes](#patch-changes-8)
            
        *   [Unstable Changes](#unstable-changes-6)
            *   [Split Route Modules (unstable)](#split-route-modules-unstable)
                
        *   [Changes by Package](#changes-by-package-4)
            
    *   [v7.1.5](#v715)
        *   [Patch Changes](#patch-changes-9)
            
    *   [v7.1.4](#v714)
        *   [Patch Changes](#patch-changes-10)
            
    *   [v7.1.3](#v713)
        *   [Patch Changes](#patch-changes-11)
            
    *   [v7.1.2](#v712)
        *   [Patch Changes](#patch-changes-12)
            
    *   [v7.1.1](#v711)
        *   [Patch Changes](#patch-changes-13)
            
    *   [v7.1.0](#v710)
        *   [Minor Changes](#minor-changes-5)
            
        *   [Patch Changes](#patch-changes-14)
            
        *   [Changes by Package](#changes-by-package-5)
            
    *   [v7.0.2](#v702)
        *   [Patch Changes](#patch-changes-15)
            
    *   [v7.0.1](#v701)
        *   [Patch Changes](#patch-changes-16)
            
    *   [v7.0.0](#v700)
        *   [Breaking Changes](#breaking-changes)
            *   [Package Restructuring](#package-restructuring)
                
            *   [Removed Adapter Re-exports](#removed-adapter-re-exports)
                
            *   [Removed APIs](#removed-apis)
                
            *   [Minimum Versions](#minimum-versions)
                
            *   [Adopted Future Flag Behaviors](#adopted-future-flag-behaviors)
                
            *   [Vite Compiler](#vite-compiler)
                
            *   [Exposed Router Promises](#exposed-router-promises)
                
        *   [Other Notable Changes](#other-notable-changes)
            *   [`routes.ts`](#routests)
                
            *   [Typesafety improvements](#typesafety-improvements)
                
            *   [Prerendering](#prerendering)
                
        *   [Major Changes (`react-router`)](#major-changes-react-router)
            
        *   [Major Changes (`@react-router/*`)](#major-changes-react-router-1)
            
        *   [Minor Changes](#minor-changes-6)
            
        *   [Patch Changes](#patch-changes-17)
            
        *   [Changes by Package](#changes-by-package-6)
            
*   [React Router v6 Releases](#react-router-v6-releases)
    *   [v6.30.0](#v6300)
        *   [Minor Changes](#minor-changes-7)
            
        *   [Patch Changes](#patch-changes-18)
            
    *   [v6.29.0](#v6290)
        *   [Minor Changes](#minor-changes-8)
            
        *   [Patch Changes](#patch-changes-19)
            
    *   [v6.28.2](#v6282)
        *   [Patch Changes](#patch-changes-20)
            
    *   [v6.28.1](#v6281)
        *   [Patch Changes](#patch-changes-21)
            
    *   [v6.28.0](#v6280)
        *   [What's Changed](#whats-changed-3)
            
        *   [Minor Changes](#minor-changes-9)
            
        *   [Patch Changes](#patch-changes-22)
            
    *   [v6.27.0](#v6270)
        *   [What's Changed](#whats-changed-4)
            *   [Stabilized APIs](#stabilized-apis)
                
        *   [Minor Changes](#minor-changes-10)
            
        *   [Patch Changes](#patch-changes-23)
            
    *   [v6.26.2](#v6262)
        *   [Patch Changes](#patch-changes-24)
            
    *   [v6.26.1](#v6261)
        *   [Patch Changes](#patch-changes-25)
            
    *   [v6.26.0](#v6260)
        *   [Minor Changes](#minor-changes-11)
            
        *   [Patch Changes](#patch-changes-26)
            
    *   [v6.25.1](#v6251)
        *   [Patch Changes](#patch-changes-27)
            
    *   [v6.25.0](#v6250)
        *   [What's Changed](#whats-changed-5)
            *   [Stabilized `v7_skipActionErrorRevalidation`](#stabilized-v7_skipactionerrorrevalidation)
                
        *   [Minor Changes](#minor-changes-12)
            
        *   [Patch Changes](#patch-changes-28)
            
    *   [v6.24.1](#v6241)
        *   [Patch Changes](#patch-changes-29)
            
    *   [v6.24.0](#v6240)
        *   [What's Changed](#whats-changed-6)
            *   [Lazy Route Discovery (a.k.a. "Fog of War")](#lazy-route-discovery-aka-fog-of-war)
                
        *   [Minor Changes](#minor-changes-13)
            
        *   [Patch Changes](#patch-changes-30)
            
    *   [v6.23.1](#v6231)
        *   [Patch Changes](#patch-changes-31)
            
    *   [v6.23.0](#v6230)
        *   [What's Changed](#whats-changed-7)
            *   [Data Strategy (unstable)](#data-strategy-unstable)
                
            *   [Skip Action Error Revalidation (unstable)](#skip-action-error-revalidation-unstable)
                
        *   [Minor Changes](#minor-changes-14)
            
    *   [v6.22.3](#v6223)
        *   [Patch Changes](#patch-changes-32)
            
    *   [v6.22.2](#v6222)
        *   [Patch Changes](#patch-changes-33)
            
    *   [v6.22.1](#v6221)
        *   [Patch Changes](#patch-changes-34)
            
    *   [v6.22.0](#v6220)
        *   [What's Changed](#whats-changed-8)
            *   [Core Web Vitals Technology Report Flag](#core-web-vitals-technology-report-flag)
                
        *   [Minor Changes](#minor-changes-15)
            
        *   [Patch Changes](#patch-changes-35)
            
    *   [v6.21.3](#v6213)
        *   [Patch Changes](#patch-changes-36)
            
    *   [v6.21.2](#v6212)
        *   [Patch Changes](#patch-changes-37)
            
    *   [v6.21.1](#v6211)
        *   [Patch Changes](#patch-changes-38)
            
    *   [v6.21.0](#v6210)
        *   [What's Changed](#whats-changed-9)
            *   [`future.v7_relativeSplatPath`](#futurev7_relativesplatpath)
                
            *   [Partial Hydration](#partial-hydration)
                
        *   [Minor Changes](#minor-changes-16)
            
        *   [Patch Changes](#patch-changes-39)
            
    *   [v6.20.1](#v6201)
        *   [Patch Changes](#patch-changes-40)
            
    *   [v6.20.0](#v6200)
        *   [Minor Changes](#minor-changes-17)
            
        *   [Patch Changes](#patch-changes-41)
            
    *   [v6.19.0](#v6190)
        *   [What's Changed](#whats-changed-10)
            *   [`unstable_flushSync` API](#unstable_flushsync-api)
                
        *   [Minor Changes](#minor-changes-18)
            
        *   [Patch Changes](#patch-changes-42)
            
    *   [v6.18.0](#v6180)
        *   [What's Changed](#whats-changed-11)
            *   [New Fetcher APIs](#new-fetcher-apis)
                
            *   [Persistence Future Flag (`future.v7_fetcherPersist`)](#persistence-future-flag-futurev7_fetcherpersist)
                
        *   [Minor Changes](#minor-changes-19)
            
        *   [Patch Changes](#patch-changes-43)
            
    *   [v6.17.0](#v6170)
        *   [What's Changed](#whats-changed-12)
            *   [View Transitions 🚀](#view-transitions-)
                
        *   [Minor Changes](#minor-changes-20)
            
        *   [Patch Changes](#patch-changes-44)
            
    *   [v6.16.0](#v6160)
        *   [Minor Changes](#minor-changes-21)
            
        *   [Patch Changes](#patch-changes-45)
            
    *   [v6.15.0](#v6150)
        *   [Minor Changes](#minor-changes-22)
            
        *   [Patch Changes](#patch-changes-46)
            
    *   [v6.14.2](#v6142)
        *   [Patch Changes](#patch-changes-47)
            
    *   [v6.14.1](#v6141)
        *   [Patch Changes](#patch-changes-48)
            
    *   [v6.14.0](#v6140)
        *   [What's Changed](#whats-changed-13)
            *   [JSON/Text Submissions](#jsontext-submissions)
                
        *   [Minor Changes](#minor-changes-23)
            
        *   [Patch Changes](#patch-changes-49)
            
    *   [v6.13.0](#v6130)
        *   [What's Changed](#whats-changed-14)
            *   [`future.v7_startTransition`](#futurev7_starttransition)
                
        *   [Minor Changes](#minor-changes-24)
            
        *   [Patch Changes](#patch-changes-50)
            
    *   [v6.12.1](#v6121)
        *   [Patch Changes](#patch-changes-51)
            
    *   [v6.12.0](#v6120)
        *   [What's Changed](#whats-changed-15)
            *   [`React.startTransition` support](#reactstarttransition-support)
                
        *   [Minor Changes](#minor-changes-25)
            
        *   [Patch Changes](#patch-changes-52)
            
    *   [v6.11.2](#v6112)
        *   [Patch Changes](#patch-changes-53)
            
    *   [v6.11.1](#v6111)
        *   [Patch Changes](#patch-changes-54)
            
    *   [v6.11.0](#v6110)
        *   [Minor Changes](#minor-changes-26)
            
        *   [Patch Changes](#patch-changes-55)
            
    *   [v6.10.0](#v6100)
        *   [What's Changed](#whats-changed-16)
            
        *   [Minor Changes](#minor-changes-27)
            *   [`future.v7_normalizeFormMethod`](#futurev7_normalizeformmethod)
                
        *   [Patch Changes](#patch-changes-56)
            
    *   [v6.9.0](#v690)
        *   [What's Changed](#whats-changed-17)
            *   [`Component`/`ErrorBoundary` route properties](#componenterrorboundary-route-properties)
                
            *   [Introducing Lazy Route Modules](#introducing-lazy-route-modules)
                
        *   [Minor Changes](#minor-changes-28)
            
        *   [Patch Changes](#patch-changes-57)
            
    *   [v6.8.2](#v682)
        *   [Patch Changes](#patch-changes-58)
            
    *   [v6.8.1](#v681)
        *   [Patch Changes](#patch-changes-59)
            
    *   [v6.8.0](#v680)
        *   [Minor Changes](#minor-changes-29)
            
        *   [Patch Changes](#patch-changes-60)
            
    *   [v6.7.0](#v670)
        *   [Minor Changes](#minor-changes-30)
            
        *   [Patch Changes](#patch-changes-61)
            
    *   [v6.6.2](#v662)
        *   [Patch Changes](#patch-changes-62)
            
    *   [v6.6.1](#v661)
        *   [Patch Changes](#patch-changes-63)
            
    *   [v6.6.0](#v660)
        *   [What's Changed](#whats-changed-18)
            
        *   [Minor Changes](#minor-changes-31)
            
        *   [Patch Changes](#patch-changes-64)
            
    *   [v6.5.0](#v650)
        *   [What's Changed](#whats-changed-19)
            
        *   [Minor Changes](#minor-changes-32)
            
        *   [Patch Changes](#patch-changes-65)
            
    *   [v6.4.5](#v645)
        *   [Patch Changes](#patch-changes-66)
            
    *   [v6.4.4](#v644)
        *   [Patch Changes](#patch-changes-67)
            
    *   [v6.4.3](#v643)
        *   [Patch Changes](#patch-changes-68)
            
    *   [v6.4.2](#v642)
        *   [Patch Changes](#patch-changes-69)
            
    *   [v6.4.1](#v641)
        *   [Patch Changes](#patch-changes-70)
            
    *   [v6.4.0](#v640)
        *   [What's Changed](#whats-changed-20)
            *   [Remix Data APIs](#remix-data-apis)
                
        *   [Patch Changes](#patch-changes-71)
            
    *   [v6.3.0](#v630)
        *   [Minor Changes](#minor-changes-33)
            
    *   [v6.2.2](#v622)
        *   [Patch Changes](#patch-changes-72)
            
    *   [v6.2.1](#v621)
        *   [Patch Changes](#patch-changes-73)
            
    *   [v6.2.0](#v620)
        *   [Minor Changes](#minor-changes-34)
            
        *   [Patch Changes](#patch-changes-74)
            
    *   [v6.1.1](#v611)
        *   [Patch Changes](#patch-changes-75)
            
    *   [v6.1.0](#v610)
        *   [Minor Changes](#minor-changes-35)
            
        *   [Patch Changes](#patch-changes-76)
            
    *   [v6.0.2](#v602)
        *   [Patch Changes](#patch-changes-77)
            
    *   [v6.0.1](#v601)
        *   [Patch Changes](#patch-changes-78)
            
    *   [v6.0.0](#v600)
        

[](#v760)
v7.6.0
----------------

Date: 2025-05-08

### [](#whats-changed)
What's Changed

#### [](#routediscovery-config-option)
`routeDiscovery` Config Option

We've added a new config option in `7.6.0` which grants you more control over the Lazy Route Discovery feature. You can now configure the `/__manifest` path if you're running multiple RR applications on the same server, or you can also disable the feature entirely if your application is small enough and the feature isn't necessary.

    // react-router.config.ts
    
    export default {
      // You can modify the manifest path used:
      routeDiscovery: { mode: "lazy", manifestPath: "/custom-manifest" }
    
      // Or you can disable this feature entirely and include all routes in the
      // manifest on initial document load:
      routeDiscovery: { mode: "initial" }
    
      // If you don't specify anything, the default config is as follows, which enables
      // Lazy Route Discovery and makes manifest requests to the `/__manifest` path:
      // routeDiscovery: { mode: "lazy", manifestPath: "/__manifest" }
    } satisfies Config;
    

#### [](#automatic-types-for-future-flags)
Automatic Types for Future Flags

Some future flags alter the way types should work in React Router. Previously, you had to remember to manually opt-in to the new types. For example, for `future.unstable_middleware`:

    // react-router.config.ts
    
    // Step 1: Enable middleware
    export default {
      future: {
        unstable_middleware: true,
      },
    };
    
    // Step 2: Enable middleware types
    declare module "react-router" {
      interface Future {
        unstable_middleware: true; // 👈 Enable middleware types
      }
    }
    

It was up to you to keep the runtime future flags synced with the types for those flags. This was confusing and error-prone.

Now, React Router will automatically enable types for future flags. That means you only need to specify the runtime future flag:

    // react-router.config.ts
    
    // Step 1: Enable middleware
    export default {
      future: {
        unstable_middleware: true,
      },
    };
    
    // No step 2! That's it!
    

Behind the scenes, React Router will generate the corresponding `declare module` into `.react-router/types`. Currently this is done in `.react-router/types/+register.ts` but this is an implementation detail that may change in the future.

### [](#minor-changes)
Minor Changes

*   `react-router` - Added a new `routeDiscovery` option in `react-router.config.ts` to configure Lazy Route Discovery behavior ([#13451](https://github.com/remix-run/react-router/pull/13451)
    )
    
*   `react-router` - Add support for route component props in `createRoutesStub` ([#13528](https://github.com/remix-run/react-router/pull/13528)
    )
    
    *   This allows you to unit test your route components using the props instead of the hooks:
        
            let RoutesStub = createRoutesStub([\
              {\
                path: "/",\
                Component({ loaderData }) {\
                  let data = loaderData as { message: string };\
                  return <pre data-testid="data">Message: {data.message}</pre>;\
                },\
                loader() {\
                  return { message: "hello" };\
                },\
              },\
            ]);
            
            render(<RoutesStub />);
            
            await waitFor(() => screen.findByText("Message: hello"));
            
        
*   `@react-router/dev` - Automatic types for future flags ([#13506](https://github.com/remix-run/react-router/pull/13506)
    )
    

### [](#patch-changes)
Patch Changes

You may notice this list is a bit larger than usual! The team ate their vegetables last week and spent the week [squashing bugs](https://x.com/BrooksLybrand/status/1918406062920589731)
 to work on lowering the issue count that had ballooned a bit since the v7 release.

*   `react-router` - Fix `react-router` module augmentation for `NodeNext` ([#13498](https://github.com/remix-run/react-router/pull/13498)
    )
*   `react-router` - Don't bundle `react-router` in `react-router/dom` CJS export ([#13497](https://github.com/remix-run/react-router/pull/13497)
    )
*   `react-router` - Fix bug where a submitting `fetcher` would get stuck in a `loading` state if a revalidating `loader` redirected ([#12873](https://github.com/remix-run/react-router/pull/12873)
    )
*   `react-router` - Fix hydration error if a server `loader` returned `undefined` ([#13496](https://github.com/remix-run/react-router/pull/13496)
    )
*   `react-router` - Fix initial load 404 scenarios in data mode ([#13500](https://github.com/remix-run/react-router/pull/13500)
    )
*   `react-router` - Stabilize `useRevalidator`'s `revalidate` function ([#13542](https://github.com/remix-run/react-router/pull/13542)
    )
*   `react-router` - Preserve status code if a `clientAction` throws a `data()` result in framework mode ([#13522](https://github.com/remix-run/react-router/pull/13522)
    )
*   `react-router` - Be defensive against leading double slashes in paths to avoid `Invalid URL` errors from the URL constructor ([#13510](https://github.com/remix-run/react-router/pull/13510)
    )
    *   Note we do not sanitize/normalize these paths - we only detect them so we can avoid the error that would be thrown by `new URL("//", window.location.origin)`
*   `react-router` - Remove `Navigator` declaration for `navigator.connection.saveData` to avoid messing with any other types beyond `saveData` in user land ([#13512](https://github.com/remix-run/react-router/pull/13512)
    )
*   `react-router` - Fix `handleError` `params` values on `.data` requests for routes with a dynamic param as the last URL segment ([#13481](https://github.com/remix-run/react-router/pull/13481)
    )
*   `react-router` - Don't trigger an `ErrorBoundary` UI before the reload when we detect a manifest version mismatch in Lazy Route Discovery ([#13480](https://github.com/remix-run/react-router/pull/13480)
    )
*   `react-router` - Inline `turbo-stream@2.4.1` dependency and fix decoding ordering of `Map`/`Set` instances ([#13518](https://github.com/remix-run/react-router/pull/13518)
    )
*   `react-router` - Only render dev warnings during dev ([#13461](https://github.com/remix-run/react-router/pull/13461)
    )
*   `react-router` - Short circuit post-processing on aborted `dataStrategy` requests ([#13521](https://github.com/remix-run/react-router/pull/13521)
    )
    *   This resolves non-user-facing console errors of the form `Cannot read properties of undefined (reading 'result')`
*   `@react-router/dev` - Support project root directories without a `package.json` if it exists in a parent directory ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - When providing a custom Vite config path via the CLI `--config`/`-c` flag, default the project root directory to the directory containing the Vite config when not explicitly provided ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - In a `routes.ts` context, ensure the `--mode` flag is respected for `import.meta.env.MODE` ([#13485](https://github.com/remix-run/react-router/pull/13485)
    )
    *   Previously, `import.meta.env.MODE` within a `routes.ts` context was always `"development"` for the `dev` and `typegen --watch` commands, but otherwise resolved to `"production"`. These defaults are still in place, but if a `--mode` flag is provided, this will now take precedence.
*   `@react-router/dev` - Ensure consistent project root directory resolution logic in CLI commands ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - When executing `react-router.config.ts` and `routes.ts` with `vite-node`, ensure that PostCSS config files are ignored ([#13489](https://github.com/remix-run/react-router/pull/13489)
    )
*   `@react-router/dev` - When extracting critical CSS during development, ensure it's loaded from the client environment to avoid issues with plugins that handle the SSR environment differently ([#13503](https://github.com/remix-run/react-router/pull/13503)
    )
*   `@react-router/dev` - Fix "Status message is not supported by HTTP/2" error during dev when using HTTPS ([#13460](https://github.com/remix-run/react-router/pull/13460)
    )
*   `@react-router/dev` - Update config when `react-router.config.ts` is created or deleted during development ([#12319](https://github.com/remix-run/react-router/pull/12319)
    )
*   `@react-router/dev` - Skip unnecessary `routes.ts` evaluation before Vite build is started ([#13513](https://github.com/remix-run/react-router/pull/13513)
    )
*   `@react-router/dev` - Fix `TS2300: Duplicate identifier` errors caused by generated types ([#13499](https://github.com/remix-run/react-router/pull/13499)
    )
*   Previously, routes that had the same full path would cause duplicate entries in the generated types for `href` (`.react-router/types/+register.ts`), causing type checking errors

### [](#unstable-changes)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Fix a few bugs with error bubbling in middleware use-cases ([#13538](https://github.com/remix-run/react-router/pull/13538)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure that `build.assetsDir` in Vite config is respected when `environments.client.build.assetsDir` is not configured ([#13491](https://github.com/remix-run/react-router/pull/13491)
    )

### [](#changes-by-package)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/create-react-router/CHANGELOG.md#760)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router/CHANGELOG.md#760)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-architect/CHANGELOG.md#760)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-cloudflare/CHANGELOG.md#760)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-dev/CHANGELOG.md#760)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-express/CHANGELOG.md#760)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-fs-routes/CHANGELOG.md#760)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-node/CHANGELOG.md#760)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#760)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-serve/CHANGELOG.md#760)
    

**Full Changelog**: [`v7.5.3...v7.6.0`](https://github.com/remix-run/react-router/compare/react-router@7.5.3...react-router@7.6.0)

[](#v753)
v7.5.3
----------------

Date: 2025-04-28

### [](#patch-changes-1)
Patch Changes

*   `react-router` - Fix bug where bubbled action errors would result in `loaderData` being cleared at the handling `ErrorBoundary` route ([#13476](https://github.com/remix-run/react-router/pull/13476)
    )
*   `react-router` - Handle redirects from `clientLoader.hydrate` initial load executions ([#13477](https://github.com/remix-run/react-router/pull/13477)
    )

**Full Changelog**: [`v7.5.2...v7.5.3`](https://github.com/remix-run/react-router/compare/react-router@7.5.2...react-router@7.5.3)

[](#v752)
v7.5.2
----------------

Date: 2025-04-24

### [](#security-notice)
Security Notice

Fixed 2 security vulnerabilities that could result in cache-poisoning attacks by sending specific headers intended for build-time usage for SPA Mode and Pre-rendering ([GHSA-f46r-rw29-r322](https://github.com/remix-run/react-router/security/advisories/GHSA-f46r-rw29-r322)
, [GHSA-cpj6-fhp6-mr6j](https://github.com/remix-run/react-router/security/advisories/GHSA-cpj6-fhp6-mr6j)
).

### [](#patch-changes-2)
Patch Changes

*   `react-router` - Adjust approach for Pre-rendering/SPA Mode via headers ([#13453](https://github.com/remix-run/react-router/pull/13453)
    )
*   `react-router` - Update Single Fetch to also handle the 204 redirects used in `?_data` requests in Remix v2 ([#13364](https://github.com/remix-run/react-router/pull/13364)
    )
    *   This allows applications to trigger a redirect on `.data` requests from outside the scope of React Router (i.e., an `express`/`hono` middleware) the same way they did in Remix v2 before Single Fetch was implemented
    *   This is a bit of an escape hatch - the recommended way to handle this is redirecting from a root route middleware
    *   To use this functionality, you may return from a `.data` request wih a response as follows:
        *   Set a 204 status code
        *   Set an `X-Remix-Redirect: <new-location>` header
        *   Optionally, set `X-Remix-Replace: true` or `X-Remix-Reload-Document: true` headers to replicate `replace()`/`redirectDocument()` functionality
    *   ⚠️ Please note that these responses rely on implementation details that are subject to change without a SemVer major release, and it is recommended you set up integration tests for your application to confirm this functionality is working correctly with each future React Router upgrade

**Full Changelog**: [`v7.5.1...v7.5.2`](https://github.com/remix-run/react-router/compare/react-router@7.5.1...react-router@7.5.2)

[](#v751)
v7.5.1
----------------

Date: 2025-04-17

### [](#patch-changes-3)
Patch Changes

*   `react-router` - When using the object-based `route.lazy` API, the `HydrateFallback` and `hydrateFallbackElement` properties are now skipped when lazy loading routes after hydration ([#13376](https://github.com/remix-run/react-router/pull/13376)
    )
    
    *   If you move the code for these properties into a separate file, since the hydrate properties were unused already (if the route wasn't present during hydration), you can avoid downloading them at all. For example:
        
            createBrowserRouter([\
              {\
                path: "/show/:showId",\
                lazy: {\
                  loader: async () => (await import("./show.loader.js")).loader,\
                  Component: async () =>\
                    (await import("./show.component.js")).Component,\
                  HydrateFallback: async () =>\
                    (await import("./show.hydrate-fallback.js")).HydrateFallback,\
                },\
              },\
            ]);
            
        
*   `react-router` - Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route ([#13253](https://github.com/remix-run/react-router/pull/13253)
    )
    
*   `react-router` - Properly revalidate pre-rendered paths when param values change when using `ssr:false` + `prerender` configs ([#13380](https://github.com/remix-run/react-router/pull/13380)
    )
    
*   `react-router` - Fix pre-rendering when a loader returns a redirect ([#13365](https://github.com/remix-run/react-router/pull/13365)
    )
    
*   `react-router` - Do not automatically add `null` to `staticHandler.query()` `context.loaderData` if routes do not have loaders ([#13223](https://github.com/remix-run/react-router/pull/13223)
    )
    
    *   This was a Remix v2 implementation detail inadvertently left in for React Router v7
    *   Now that we allow returning `undefined` from loaders, our prior check of `loaderData[routeId] !== undefined` was no longer sufficient and was changed to a `routeId in loaderData` check - these `null` values can cause issues for this new check
    *   ⚠️ This could be a "breaking bug fix" for you if you are doing manual SSR with `createStaticHandler()`/`<StaticRouterProvider>`, and using `context.loaderData` to control `<RouterProvider>` hydration behavior on the client

### [](#unstable-changes-1)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add better error messaging when `getLoadContext` is not updated to return a `Map` ([#13242](https://github.com/remix-run/react-router/pull/13242)
    )
*   `react-router` - Update context type for `LoaderFunctionArgs`/`ActionFunctionArgs` when middleware is enabled ([#13381](https://github.com/remix-run/react-router/pull/13381)
    )
*   `react-router` - Add a new `unstable_runClientMiddleware` argument to `dataStrategy` to enable middleware execution in custom `dataStrategy` implementations ([#13395](https://github.com/remix-run/react-router/pull/13395)
    )
*   `react-router` - Add support for the new `unstable_shouldCallHandler`/`unstable_shouldRevalidateArgs` APIs in `dataStrategy` ([#13253](https://github.com/remix-run/react-router/pull/13253)
    )

**Full Changelog**: [`v7.5.0...v7.5.1`](https://github.com/remix-run/react-router/compare/react-router@7.5.0...react-router@7.5.1)

[](#v750)
v7.5.0
----------------

Date: 2025-04-04

### [](#whats-changed-1)
What's Changed

#### [](#routelazy-object-api)
`route.lazy` Object API

We've introduced a new `route.lazy` API which gives you more granular control over the lazy loading of route properties that you could not achieve with the `route.lazy()` function signature. This is useful for Framework mode and performance-critical library mode applications.

    createBrowserRouter([\
      {\
        path: "/show/:showId",\
        lazy: {\
          loader: async () => (await import("./show.loader.js")).loader,\
          action: async () => (await import("./show.action.js")).action,\
          Component: async () => (await import("./show.component.js")).Component,\
        },\
      },\
    ]);
    

⚠️ This is a breaking change if you have adopted the `route.unstable_lazyMiddleware` API which has been removed in favor of `route.lazy.unstable_middleware`. See the `Unstable Changes` section below for more information.

### [](#minor-changes-1)
Minor Changes

*   `react-router` - Add granular object-based API for `route.lazy` to support lazy loading of individual route properties ([#13294](https://github.com/remix-run/react-router/pull/13294)
    )

### [](#patch-changes-4)
Patch Changes

*   `@react-router/dev` - Update optional `wrangler` peer dependency range to support `wrangler` v4 ([#13258](https://github.com/remix-run/react-router/pull/13258)
    )
*   `@react-router/dev` - Reinstate dependency optimization in the child compiler to fix `depsOptimizer is required in dev mode` errors when using `vite-plugin-cloudflare` and importing Node.js builtins ([#13317](https://github.com/remix-run/react-router/pull/13317)
    )

### [](#unstable-changes-2)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Introduce `future.unstable_subResourceIntegrity` flag that enables generation of an `importmap` with `integrity` for the scripts that will be loaded by the browser ([#13163](https://github.com/remix-run/react-router/pull/13163)
    )
*   `react-router` - Remove support for the `route.unstable_lazyMiddleware` property ([#13294](https://github.com/remix-run/react-router/pull/13294)
    )
    *   In order to lazily load middleware, you can use the new object-based `route.lazy.unstable_middleware` API
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure critical CSS in development works when using a custom Vite `base` has been configured ([#13305](https://github.com/remix-run/react-router/pull/13305)
    )

### [](#changes-by-package-1)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/create-react-router/CHANGELOG.md#750)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router/CHANGELOG.md#750)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-architect/CHANGELOG.md#750)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-cloudflare/CHANGELOG.md#750)
    
*   [`@react-router/dev`](http://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-dev/CHANGELOG.md#750)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-express/CHANGELOG.md#750)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-fs-routes/CHANGELOG.md#750)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-node/CHANGELOG.md#750)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#750)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-serve/CHANGELOG.md#750)
    

**Full Changelog**: [`v7.4.1...v7.5.0`](https://github.com/remix-run/react-router/compare/react-router@7.4.1...react-router@7.5.0)

[](#v741)
v7.4.1
----------------

Date: 2025-03-28

### [](#security-notice-1)
Security Notice

Fixed a security vulnerability that allowed URL manipulation and potential cache pollution via the `Host` and `X-Forwarded-Host` headers due to inadequate port sanitization ([GHSA-4q56-crqp-v477/CVE-2025-31137](https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477)
).

### [](#patch-changes-5)
Patch Changes

*   `react-router` - Dedupe calls to `route.lazy` functions ([#13260](https://github.com/remix-run/react-router/pull/13260)
    )
*   `@react-router/dev` - Fix path in prerender error messages ([#13257](https://github.com/remix-run/react-router/pull/13257)
    )
*   `@react-router/dev` - Fix typegen for virtual modules when `moduleDetection` is set to `force` ([#13267](https://github.com/remix-run/react-router/pull/13267)
    )
*   `@react-router/express` - Better validation of `x-forwarded-host` header to prevent potential security issues ([#13309](https://github.com/remix-run/react-router/pull/13309)
    )

### [](#unstable-changes-3)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Fix types on `unstable_MiddlewareFunction` to avoid type errors when a middleware doesn't return a value ([#13311](https://github.com/remix-run/react-router/pull/13311)
    )
*   `react-router` - Add support for `route.unstable_lazyMiddleware` function to allow lazy loading of middleware logic ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )
    *   ⚠️ We do not recommend adoption of this API currently as we are likely going to change it prior to the stable release of middleware
    *   ⚠️ This may be a breaking change if your app is currently returning `unstable_middleware` from `route.lazy`
    *   The `route.unstable_middleware` property is no longer supported in the return value from `route.lazy`
    *   If you want to lazily load middleware, you must use `route.unstable_lazyMiddleware`
*   `@react-router/dev` - When both `future.unstable_middleware` and `future.unstable_splitRouteModules` are enabled, split `unstable_clientMiddleware` route exports into separate chunks when possible ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )
*   `@react-router/dev` - Improve performance of `future.unstable_middleware` by ensuring that route modules are only blocking during the middleware phase when the `unstable_clientMiddleware` has been defined ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )

**Full Changelog**: [`v7.4.0...v7.4.1`](https://github.com/remix-run/react-router/compare/react-router@7.4.0...react-router@7.4.1)

[](#v740)
v7.4.0
----------------

Date: 2025-03-19

### [](#minor-changes-2)
Minor Changes

*   `@react-router/dev` - Generate types for `virtual:react-router/server-build` module ([#13152](https://github.com/remix-run/react-router/pull/13152)
    )

### [](#patch-changes-6)
Patch Changes

*   `react-router` - Fix root loader data on initial load redirects in SPA mode ([#13222](https://github.com/remix-run/react-router/pull/13222)
    )
*   `react-router` - Load ancestor pathless/index routes in lazy route discovery for upwards non-eager-discovery routing ([#13203](https://github.com/remix-run/react-router/pull/13203)
    )
*   `react-router` - Fix `shouldRevalidate` behavior for `clientLoader`\-only routes in `ssr:true` apps ([#13221](https://github.com/remix-run/react-router/pull/13221)
    )
*   `@react-router/dev` - Fix conflicts with other Vite plugins that use the `configureServer` and/or `configurePreviewServer` hooks ([#13184](https://github.com/remix-run/react-router/pull/13184)
    )

### [](#unstable-changes-4)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - If a middleware throws an error, ensure we only bubble the error itself via `next()` and are no longer leaking the `MiddlewareError` implementation detail ([#13180](https://github.com/remix-run/react-router/pull/13180)
    )
    *   ⚠️ This may be a breaking change if you are `catch`\-ing errors thrown by the `next()` function in your middlewares
*   `react-router` - Fix `RequestHandler` `loadContext` parameter type when middleware is enabled ([#13204](https://github.com/remix-run/react-router/pull/13204)
    )
*   `react-router` - Update `Route.unstable_MiddlewareFunction` to have a return value of `Response | undefined` instead of `Response | void` ([#13199](https://github.com/remix-run/react-router/pull/13199)
    )
*   `@react-router/dev` - When `future.unstable_splitRouteModules` is set to `"enforce"`, allow both splittable and unsplittable root route exports since it's always in a single chunk ([#13238](https://github.com/remix-run/react-router/pull/13238)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, allow plugins that override the default SSR environment (such as `@cloudflare/vite-plugin`) to be placed before or after the React Router plugin ([#13183](https://github.com/remix-run/react-router/pull/13183)
    )

### [](#changes-by-package-2)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/create-react-router/CHANGELOG.md#740)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router/CHANGELOG.md#740)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-architect/CHANGELOG.md#740)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-cloudflare/CHANGELOG.md#740)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-dev/CHANGELOG.md#740)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-express/CHANGELOG.md#740)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-fs-routes/CHANGELOG.md#740)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-node/CHANGELOG.md#740)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#740)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-serve/CHANGELOG.md#740)
    

**Full Changelog**: [`v7.3.0...v7.4.0`](https://github.com/remix-run/react-router/compare/react-router@7.3.0...react-router@7.4.0)

[](#v730)
v7.3.0
----------------

Date: 2025-03-06

### [](#minor-changes-3)
Minor Changes

*   Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13061](https://github.com/remix-run/react-router/pull/13061)
    )

### [](#patch-changes-7)
Patch Changes

*   `react-router` - Detect and handle manifest-skew issues on new deploys during active sessions ([#13061](https://github.com/remix-run/react-router/pull/13061)
    )
    *   In framework mode, Lazy Route Discovery will now detect manifest version mismatches in active sessions after a new deploy
    *   On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
    *   On `fetcher` calls to undiscovered routes, this mismatch will trigger a document reload of the current path
*   `react-router` - Skip resource route flow in dev server in SPA mode ([#13113](https://github.com/remix-run/react-router/pull/13113)
    )
*   `react-router` - Fix single fetch `_root.data` requests when a `basename` is used ([#12898](https://github.com/remix-run/react-router/pull/12898)
    )
*   `react-router` - Fix types for `loaderData` and `actionData` that contained `Record`s ([#13139](https://github.com/remix-run/react-router/pull/13139)
    )
    *   ⚠️ This is a breaking change for users who have already adopted `unstable_SerializesTo` - see the note in the `Unstable Changes` section below for more information
*   `@react-router/dev` - Fix support for custom client `build.rollupOptions.output.entryFileNames` ([#13098](https://github.com/remix-run/react-router/pull/13098)
    )
*   `@react-router/dev` - Fix usage of `prerender` option when `serverBundles` option has been configured or provided by a preset, e.g. `vercelPreset` from `@vercel/react-router` ([#13082](https://github.com/remix-run/react-router/pull/13082)
    )
*   `@react-router/dev` - Fix support for custom `build.assetsDir` ([#13077](https://github.com/remix-run/react-router/pull/13077)
    )
*   `@react-router/dev` - Remove unused dependencies ([#13134](https://github.com/remix-run/react-router/pull/13134)
    )
*   `@react-router/dev` - Stub all routes except root in "SPA Mode" server builds to avoid issues when route modules or their dependencies import non-SSR-friendly modules ([#13023](https://github.com/remix-run/react-router/pull/13023)
    )
*   `@react-router/dev` - Remove unused Vite file system watcher ([#13133](https://github.com/remix-run/react-router/pull/13133)
    )
*   `@react-router/dev` - Fix support for custom SSR build input when `serverBundles` option has been configured ([#13107](https://github.com/remix-run/react-router/pull/13107)
    )
    *   ⚠️ Note that for consumers using the `future.unstable_viteEnvironmentApi` and `serverBundles` options together, hyphens are no longer supported in server bundle IDs since they also need to be valid Vite environment names.
*   `@react-router/dev` - Fix dev server when using HTTPS by stripping HTTP/2 pseudo headers from dev server requests ([#12830](https://github.com/remix-run/react-router/pull/12830)
    )
*   `@react-router/dev` - Lazy load Cloudflare platform proxy on first dev server request when using the `cloudflareDevProxy` Vite plugin to avoid creating unnecessary `workerd` processes ([#13016](https://github.com/remix-run/react-router/pull/13016)
    )
*   `@react-router/dev` - Fix duplicated entries in typegen for layout routes and their corresponding index route ([#13140](https://github.com/remix-run/react-router/pull/13140)
    )
*   `@react-router/express` - Update `express` `peerDependency` to include v5 ([https://github.com/remix-run/react-router/pull/13064](https://github.com/remix-run/react-router/pull/13064)
    ) ([#12961](https://github.com/remix-run/react-router/pull/12961)
    )

### [](#unstable-changes-5)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add `context` support to client side data routers (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941)
    )
*   `react-router` - Support middleware on routes (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941)
    )
*   `@react-router/dev` - Fix errors with `future.unstable_viteEnvironmentApi` when the `ssr` environment has been configured by another plugin to be a custom `Vite.DevEnvironment` rather than the default `Vite.RunnableDevEnvironment` ([#13008](https://github.com/remix-run/react-router/pull/13008)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled and the `ssr` environment has `optimizeDeps.noDiscovery` disabled, define `optimizeDeps.entries` and `optimizeDeps.include` ([#13007](https://github.com/remix-run/react-router/pull/13007)
    )

#### [](#client-side-context-unstable)
Client-side `context` (unstable)

Your application `clientLoader`/`clientAction` functions (or `loader`/`action` in library mode) will now receive a `context` parameter on the client. This is an instance of `unstable_RouterContextProvider` that you use with type-safe contexts (similar to `React.createContext`) and is most useful with the corresponding `unstable_clientMiddleware` API:

    import { unstable_createContext } from "react-router";
    
    type User = {
      /*...*/
    };
    
    const userContext = unstable_createContext<User>();
    
    const sessionMiddleware: Route.unstable_ClientMiddlewareFunction = async ({
      context,
    }) => {
      let user = await getUser();
      context.set(userContext, user);
    };
    
    export const unstable_clientMiddleware = [sessionMiddleware];
    
    export function clientLoader({ context }: Route.ClientLoaderArgs) {
      let user = context.get(userContext);
      let profile = await getProfile(user.id);
      return { profile };
    }
    

Similar to server-side requests, a fresh `context` will be created per navigation (or `fetcher` call). If you have initial data you'd like to populate in the context for every request, you can provide an `unstable_getContext` function at the root of your app:

*   Library mode - `createBrowserRouter(routes, { unstable_getContext })`
*   Framework mode - `<HydratedRouter unstable_getContext>`

This function should return an value of type `unstable_InitialContext` which is a `Map<unstable_RouterContext, unknown>` of context's and initial values:

    const loggerContext = unstable_createContext<(...args: unknown[]) => void>();
    
    function logger(...args: unknown[]) {
      console.log(new Date.toISOString(), ...args);
    }
    
    function unstable_getContext() {
      let map = new Map();
      map.set(loggerContext, logger);
      return map;
    }
    

#### [](#middleware-unstable)
Middleware (unstable)

Middleware is implemented behind a `future.unstable_middleware` flag. To enable, you must enable the flag and the types in your `react-router.config.ts` file:

    import type { Config } from "@react-router/dev/config";
    import type { Future } from "react-router";
    
    declare module "react-router" {
      interface Future {
        unstable_middleware: true; // 👈 Enable middleware types
      }
    }
    
    export default {
      future: {
        unstable_middleware: true, // 👈 Enable middleware
      },
    } satisfies Config;
    

⚠️ Middleware is unstable and should not be adopted in production. There is at least one known de-optimization in route module loading for `clientMiddleware` that we will be addressing this before a stable release.

⚠️ Enabling middleware contains a breaking change to the `context` parameter passed to your `loader`/`action` functions - see below for more information.

Once enabled, routes can define an array of middleware functions that will run sequentially before route handlers run. These functions accept the same parameters as `loader`/`action` plus an additional `next` parameter to run the remaining data pipeline. This allows middlewares to perform logic before and after handlers execute.

    // Framework mode
    export const unstable_middleware = [serverLogger, serverAuth]; // server
    export const unstable_clientMiddleware = [clientLogger]; // client
    
    // Library mode
    const routes = [\
      {\
        path: "/",\
        // Middlewares are client-side for library mode SPA's\
        unstable_middleware: [clientLogger, clientAuth],\
        loader: rootLoader,\
        Component: Root,\
      },\
    ];
    

Here's a simple example of a client-side logging middleware that can be placed on the root route:

    const clientLogger: Route.unstable_ClientMiddlewareFunction = async (
      { request },
      next
    ) => {
      let start = performance.now();
    
      // Run the remaining middlewares and all route loaders
      await next();
    
      let duration = performance.now() - start;
      console.log(`Navigated to ${request.url} (${duration}ms)`);
    };
    

Note that in the above example, the `next`/`middleware` functions don't return anything. This is by design as on the client there is no "response" to send over the network like there would be for middlewares running on the server. The data is all handled behind the scenes by the stateful `router`.

For a server-side middleware, the `next` function will return the HTTP `Response` that React Router will be sending across the wire, thus giving you a chance to make changes as needed. You may throw a new response to short circuit and respond immediately, or you may return a new or altered response to override the default returned by `next()`.

    const serverLogger: Route.unstable_MiddlewareFunction = async (
      { request, params, context },
      next
    ) => {
      let start = performance.now();
    
      // 👇 Grab the response here
      let res = await next();
    
      let duration = performance.now() - start;
      console.log(`Navigated to ${request.url} (${duration}ms)`);
    
      // 👇 And return it here (optional if you don't modify the response)
      return res;
    };
    

You can throw a `redirect` from a middleware to short circuit any remaining processing:

    import { sessionContext } from "../context";
    const serverAuth: Route.unstable_MiddlewareFunction = (
      { request, params, context },
      next
    ) => {
      let session = context.get(sessionContext);
      let user = session.get("user");
      if (!user) {
        session.set("returnTo", request.url);
        throw redirect("/login", 302);
      }
    };
    

_Note that in cases like this where you don't need to do any post-processing you don't need to call the `next` function or return a `Response`._

Here's another example of using a server middleware to detect 404s and check the CMS for a redirect:

    const redirects: Route.unstable_MiddlewareFunction = async ({
      request,
      next,
    }) => {
      // attempt to handle the request
      let res = await next();
    
      // if it's a 404, check the CMS for a redirect, do it last
      // because it's expensive
      if (res.status === 404) {
        let cmsRedirect = await checkCMSRedirects(request.url);
        if (cmsRedirect) {
          throw redirect(cmsRedirect, 302);
        }
      }
    
      return res;
    };
    

For more information on the `middleware` API/design, please see the [decision doc](https://github.com/remix-run/react-router/blob/release-next/decisions/0014-context-middleware.md)
.

##### [](#middleware-context-parameter)
Middleware `context` parameter

When middleware is enabled, your application will use a different type of `context` parameter in your loaders and actions to provide better type safety. Instead of `AppLoadContext`, `context` will now be an instance of `ContextProvider` that you can use with type-safe contexts (similar to `React.createContext`):

    import { unstable_createContext } from "react-router";
    import { Route } from "./+types/root";
    import type { Session } from "./sessions.server";
    import { getSession } from "./sessions.server";
    
    let sessionContext = unstable_createContext<Session>();
    
    const sessionMiddleware: Route.unstable_MiddlewareFunction = ({
      context,
      request,
    }) => {
      let session = await getSession(request);
      context.set(sessionContext, session);
      //                          ^ must be of type Session
    };
    
    // ... then in some downstream middleware
    const loggerMiddleware: Route.unstable_MiddlewareFunction = ({
      context,
      request,
    }) => {
      let session = context.get(sessionContext);
      //  ^ typeof Session
      console.log(session.get("userId"), request.method, request.url);
    };
    
    // ... or some downstream loader
    export function loader({ context }: Route.LoaderArgs) {
      let session = context.get(sessionContext);
      let profile = await getProfile(session.get("userId"));
      return { profile };
    }
    

If you are using a custom server with a `getLoadContext` function, the return value for initial context values passed from the server adapter layer is no longer an object and should now return an `unstable_InitialContext` (`Map<RouterContext, unknown>`):

    let adapterContext = unstable_createContext<MyAdapterContext>();
    
    function getLoadContext(req, res): unstable_InitialContext {
      let map = new Map();
      map.set(adapterContext, getAdapterContext(req));
      return map;
    }
    

#### [](#unstable_serializesto)
`unstable_SerializesTo`

`unstable_SerializesTo` added a way to register custom serialization types in Single Fetch for other library and framework authors like Apollo. It was implemented with branded type whose branded property that was made optional so that casting arbitrary values was easy:

    // without the brand being marked as optional
    let x1 = 42 as unknown as unstable_SerializesTo<number>;
    //          ^^^^^^^^^^
    
    // with the brand being marked as optional
    let x2 = 42 as unstable_SerializesTo<number>;
    

However, this broke type inference in `loaderData` and `actionData` for any `Record` types as those would now (incorrectly) match `unstable_SerializesTo`. This affected all users, not just those that depended on `unstable_SerializesTo`. To fix this, the branded property of `unstable_SerializesTo` is marked as required instead of optional.

For library and framework authors using `unstable_SerializesTo`, you may need to add `as unknown` casts before casting to `unstable_SerializesTo`.

### [](#changes-by-package-3)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/create-react-router/CHANGELOG.md#730)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router/CHANGELOG.md#730)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-architect/CHANGELOG.md#730)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-cloudflare/CHANGELOG.md#730)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-dev/CHANGELOG.md#730)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-express/CHANGELOG.md#730)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-fs-routes/CHANGELOG.md#730)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-node/CHANGELOG.md#730)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#730)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-serve/CHANGELOG.md#730)
    

**Full Changelog**: [`v7.2.0...v7.3.0`](https://github.com/remix-run/react-router/compare/react-router@7.2.0...react-router@7.3.0)

[](#v720)
v7.2.0
----------------

Date: 2025-02-18

### [](#whats-changed-2)
What's Changed

#### [](#type-safe-href-utility)
Type-safe `href` utility

In framework mode, we now provide you with a fully type-safe `href` utility to give you all the warm and fuzzy feelings of path auto-completion and param validation for links in your application:

    import { href } from "react-router";
    
    export default function Component() {
      const link = href("/blog/:slug", { slug: "my-first-post" });
      //                ^ type-safe!     ^ Also type-safe!
    
      return (
        <main>
          <Link to={href("/products/:id", { id: "asdf" })} />
          <NavLink to={href("/:lang?/about", { lang: "en" })} />
        </main>
      );
    }
    

You'll now get type errors if you pass a bad path value or a bad param value:

    const badPath = href("/not/a/valid/path");
    //                   ^ Error!
    
    const badParam = href("/blog/:slug", { oops: "bad param" });
    //                                     ^ Error!
    

#### [](#prerendering-with-a-spa-fallback)
Prerendering with a SPA Fallback

This release enhances the ability to use a combination of pre-rendered paths alongside other paths that operate in "SPA Mode" when pre-rendering with `ssr:false`.

*   If you specify `ssr:false` without a `prerender` config, this is considered "SPA Mode" and the generated `index.html` file will only render down to the root route and will be able to hydrate for any valid application path
*   If you specify `ssr:false` with a `prerender` config but _do not_ include the `/` path (i.e., `prerender: ['/blog/post']`), then we still generate a "SPA Mode" `index.html` file that can hydrate for any path in the application
*   If you specify `ssr:false` and include the `/` path in your `prerender` config, the generated `index.html` file will be specific to the root index route, so we will now also generate a separate "SPA Mode" file in `__spa-fallback.html` that you can serve/hydrate for non-prerendered paths

For more info, see the [Pre-rendering](https://reactrouter.com/dev/how-to/pre-rendering#pre-rendering-with-a-spa-fallback)
 docs for more info.

#### [](#allow-a-root-loader-in-spa-mode)
Allow a root `loader` in SPA Mode

SPA Mode used to prohibit the use of loaders in all routes so that we could hydrate for any path in the application. However, because the root route is always rendered at build time, we can lift this restriction for the root route.

In order to use your build-time loader data during pre-rendering, we now also expose the `loaderData` as an optional prop for the `HydrateFallback` component on routes:

*   This will be defined so long as the `HydrateFallback` is rendering because _children_ routes are loading
*   This will be `undefined` if the `HydrateFallback` is rendering because the route itself has it's own hydrating `clientLoader`
    *   In SPA mode, this will allow you to render loader root data into the SPA Mode HTML file

### [](#minor-changes-4)
Minor Changes

*   `react-router` - New type-safe `href` utility that guarantees links point to actual paths in your app ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )
*   `@react-router/dev` - Generate a "SPA fallback" HTML file when pre-rendering the `/` route with `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
*   `@react-router/dev` - Allow a `loader` in the root route in SPA mode because it can be called/server-rendered at build time ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   `Route.HydrateFallbackProps` now also receives `loaderData`

### [](#patch-changes-8)
Patch Changes

*   `react-router` - Disable Lazy Route Discovery for all `ssr:false` apps and not just "SPA Mode" because there is no runtime server to serve the search-param-configured `__manifest` requests ([#12894](https://github.com/remix-run/react-router/pull/12894)
    )
    *   We previously only disabled this for "SPA Mode" but we realized it should apply to all `ssr:false` apps
    *   In those `prerender` scenarios we would pre-render the `/__manifest` file but that makes some unnecessary assumptions about the static file server behaviors
*   `react-router` - Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
*   `react-router` - Properly handle revalidations to across a pre-render/SPA boundary ([#13021](https://github.com/remix-run/react-router/pull/13021)
    )
    *   In "hybrid" applications where some routes are pre-rendered and some are served from a SPA fallback, we need to avoid making `.data` requests if the path wasn't pre-rendered because the request will 404
    *   We don't know all the pre-rendered paths client-side, however:
        *   All `loader` data in `ssr:false` mode is static because it's generated at build time
        *   A route must use a `clientLoader` to do anything dynamic
        *   Therefore, if a route only has a `loader` and not a `clientLoader`, we disable revalidation by default because there is no new data to retrieve
        *   We short circuit and skip single fetch `.data` request logic if there are no server loaders with `shouldLoad=true` in our single fetch `dataStrategy`
        *   This ensures that the route doesn't cause a `.data` request that would 404 after a submission
*   `react-router` - Align dev server behavior with static file server behavior when `ssr:false` is set ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   When no `prerender` config exists, only SSR down to the root `HydrateFallback` (SPA Mode)
    *   When a `prerender` config exists but the current path is not pre-rendered, only SSR down to the root `HydrateFallback` (SPA Fallback)
    *   Return a 404 on `.data` requests to non-pre-rendered paths
*   `react-router` - Improve prefetch performance of CSS side effects in framework mode ([#12889](https://github.com/remix-run/react-router/pull/12889)
    )
*   `react-router` - Properly handle interrupted manifest requests in lazy route discovery ([#12915](https://github.com/remix-run/react-router/pull/12915)
    )
*   `@react-router/dev` - Handle custom `envDir` in Vite config ([#12969](https://github.com/remix-run/react-router/pull/12969)
    )
*   `@react-router/dev` - Fix CLI parsing to allow argument-less `npx react-router` usage ([#12925](https://github.com/remix-run/react-router/pull/12925)
    )
*   `@react-router/dev` - Skip action-only resource routes when using `prerender:true` ([#13004](https://github.com/remix-run/react-router/pull/13004)
    )
*   `@react-router/dev` - Enhance invalid export detection when using `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   `headers`/`action` functions are prohibited in all routes with `ssr:false` because there will be no runtime server on which to run them
    *   `loader` functions are more nuanced and depend on whether a given route is prerendered
        *   When using `ssr:false` without a `prerender` config, only the `root` route can have a `loader`
        *   When using `ssr:false` with a `prerender` config, only routes matched by a `prerender` path can have a `loader`
*   `@react-router/dev` - Error at build time in `ssr:false` + `prerender` apps for the edge case scenario of: ([#13021](https://github.com/remix-run/react-router/pull/13021)
    )
    *   A parent route has only a `loader` (does not have a `clientLoader`)
    *   The parent route is pre-rendered
    *   The parent route has children routes which are not prerendered
    *   This means that when the child paths are loaded via the SPA fallback, the parent won't have any `loaderData` because there is no server on which to run the `loader`
    *   This can be resolved by either adding a parent `clientLoader` or pre-rendering the child paths
    *   If you add a `clientLoader`, calling the `serverLoader()` on non-prerendered paths will throw a 404
*   `@react-router/dev` - Limit prerendered resource route `.data` files to only the target route ([#13004](https://github.com/remix-run/react-router/pull/13004)
    )
*   `@react-router/dev` - Fix pre-rendering of binary files ([#13039](https://github.com/remix-run/react-router/pull/13039)
    )
*   `@react-router/dev` - Fix typegen for repeated params ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )
    *   In React Router, path parameters are keyed by their name, so for a path pattern like `/a/:id/b/:id?/c/:id`, the last `:id` will set the value for `id` in `useParams` and the `params` prop
        *   For example, `/a/1/b/2/c/3` will result in the value `{ id: 3 }` at runtime
    *   Previously, generated types for params incorrectly modeled repeated params with an array
        *   For example, `/a/1/b/2/c/3` generated a type like `{ id: [1,2,3] }`.
    *   To be consistent with runtime behavior, the generated types now correctly model the "last one wins" semantics of path parameters.
        *   For example, `/a/1/b/2/c/3` now generates a type like `{ id: 3 }`.
*   `@react-router/dev` - Fix path to load `package.json` for `react-router --version` ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )

### [](#unstable-changes-6)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add `unstable_SerializesTo` brand type for library authors to register types serializable by React Router's streaming format (`turbo-stream`) ([#12264](https://github.com/remix-run/react-router/pull/12264)
    )
*   `@react-router/dev` - Add unstable support for splitting route modules in framework mode via `future.unstable_splitRouteModules` ([#11871](https://github.com/remix-run/react-router/pull/11871)
    )
*   `@react-router/dev` - Add `future.unstable_viteEnvironmentApi` flag to enable experimental Vite Environment API support ([#12936](https://github.com/remix-run/react-router/pull/12936)
    )

#### [](#split-route-modules-unstable)
Split Route Modules (unstable)

> ⚠️ This feature is currently [unstable](https://reactrouter.com/community/api-development-strategy#unstable-flags)
> , enabled by the `future.unstable_splitRouteModules` flag. We’d love any interested users to play with it locally and provide feedback, but we do not recommend using it in production yet.
> 
> If you do choose to adopt this flag in production, please ensure you do sufficient testing against your production build to ensure that the optimization is working as expected.

One of the conveniences of the [Route Module API](https://reactrouter.com/start/framework/route-module)
 is that everything a route needs is in a single file. Unfortunately this comes with a performance cost in some cases when using the `clientLoader`, `clientAction`, and `HydrateFallback` APIs.

As a basic example, consider this route module:

    import { MassiveComponent } from "~/components";
    
    export async function clientLoader() {
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      return <MassiveComponent data={loaderData} />;
    }
    

In this example we have a minimal `clientLoader` export that makes a basic fetch call, whereas the default component export is much larger. This is a problem for performance because it means that if we want to navigate to this route client-side, the entire route module must be downloaded before the client loader can start running.

To visualize this as a timeline:

In the following timeline diagrams, different characters are used within the Route Module bars to denote the different Route Module APIs being exported.

    Get Route Module:  |--=======|
    Run clientLoader:            |-----|
    Render:                            |-|
    

Instead, we want to optimize this to the following:

    Get clientLoader:  |--|
    Get Component:     |=======|
    Run clientLoader:     |-----|
    Render:                     |-|
    

To achieve this optimization, React Router will split the route module into multiple smaller modules during the production build process. In this case, we'll end up with two separate [virtual modules](https://vite.dev/guide/api-plugin#virtual-modules-convention)
 — one for the client loader and one for the component and its dependencies.

    export async function clientLoader() {
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    

    import { MassiveComponent } from "~/components";
    
    export default function Component({ loaderData }) {
      return <MassiveComponent data={loaderData} />;
    }
    

> 💡 This optimization is automatically applied in framework mode, but you can also implement it in library mode via `route.lazy` and authoring your route in multiple files as covered in our blog post on [lazy loading route modules.](https://remix.run/blog/lazy-loading-routes#advanced-usage-and-optimizations)

Now that these are available as separate modules, the client loader and the component can be downloaded in parallel. This means that the client loader can be executed as soon as it's ready without having to wait for the component.

This optimization is even more pronounced when more Route Module APIs are used. For example, when using `clientLoader`, `clientAction` and `HydrateFallback`, the timeline for a single route module during a client-side navigation might look like this:

    Get Route Module:     |--~~++++=======|
    Run clientLoader:                     |-----|
    Render:                                     |-|
    

This would instead be optimized to the following:

    Get clientLoader:     |--|
    Get clientAction:     |~~|
    Get HydrateFallback:  SKIPPED
    Get Component:        |=======|
    Run clientLoader:        |-----|
    Render:                        |-|
    

Note that this optimization only works when the Route Module APIs being split don't share code within the same file. For example, the following route module can't be split:

    import { MassiveComponent } from "~/components";
    
    const shared = () => console.log("hello");
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

This route will still work, but since both the client loader and the component depend on the `shared` function defined within the same file, it will be de-optimized into a single route module.

To avoid this, you can extract any code shared between exports into a separate file. For example:

    export const shared = () => console.log("hello");
    

You can then import this shared code in your route module without triggering the de-optimization:

    import { MassiveComponent } from "~/components";
    import { shared } from "./shared";
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

Since the shared code is in its own module, React Router is now able to split this route module into two separate virtual modules:

    import { shared } from "./shared";
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    

    import { MassiveComponent } from "~/components";
    import { shared } from "./shared";
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

If your project is particularly performance sensitive, you can set the `unstable_splitRouteModules` future flag to `"enforce"`:

    export default {
      future: {
        unstable_splitRouteModules: "enforce",
      },
    };
    

This setting will raise an error if any route modules can't be split:

    Error splitting route module: routes/example/route.tsx
    
    - clientLoader
    
    This export could not be split into its own chunk because it shares code with other exports. You should extract any shared code into its own module and then import it within the route module.
    

### [](#changes-by-package-4)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/create-react-router/CHANGELOG.md#720)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router/CHANGELOG.md#720)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-architect/CHANGELOG.md#720)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-cloudflare/CHANGELOG.md#720)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-dev/CHANGELOG.md#720)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-express/CHANGELOG.md#720)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-fs-routes/CHANGELOG.md#720)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-node/CHANGELOG.md#720)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#720)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-serve/CHANGELOG.md#720)
    

**Full Changelog**: [`v7.1.5...v7.2.0`](https://github.com/remix-run/react-router/compare/react-router@7.1.5...react-router@7.2.0)

[](#v715)
v7.1.5
----------------

Date: 2025-01-31

### [](#patch-changes-9)
Patch Changes

*   `react-router` - Fix regression introduced in `7.1.4` via [#12800](https://github.com/remix-run/react-router/pull/12800)
     that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#12927](https://github.com/remix-run/react-router/pull/12927)
    )

**Full Changelog**: [`v7.1.4...v7.1.5`](https://github.com/remix-run/react-router/compare/react-router@7.1.4...react-router@7.1.5)

[](#v714)
v7.1.4
----------------

Date: 2025-01-30

### [](#patch-changes-10)
Patch Changes

*   `@react-router/dev` - Properly resolve Windows file paths to scan for Vite's dependency optimization when using the `unstable_optimizeDeps` future flag ([#12637](https://github.com/remix-run/react-router/pull/12637)
    )
*   `@react-router/dev` - Fix prerendering when using a custom server - previously we ended up trying to import the users custom server when we actually want to import the virtual server build module ([#12759](https://github.com/remix-run/react-router/pull/12759)
    )
*   `react-router` - Properly handle status codes that cannot have a body in single fetch responses (204, etc.) ([#12760](https://github.com/remix-run/react-router/pull/12760)
    )
*   `react-router` - Properly bubble headers as `errorHeaders` when throwing a `data()` result ([#12846](https://github.com/remix-run/react-router/pull/12846)
    )
    *   Avoid duplication of `Set-Cookie` headers if also returned from `headers`
*   `react-router` - Stop erroring on resource routes that return raw strings/objects and instead serialize them as `text/plain` or `application/json` responses ([#12848](https://github.com/remix-run/react-router/pull/12848)
    )
    *   This only applies when accessed as a resource route without the `.data` extension
    *   When accessed from a Single Fetch `.data` request, they will still be encoded via `turbo-stream`
*   `react-router` - Optimize Lazy Route Discovery path discovery to favor a single `querySelectorAll` call at the `body` level instead of many calls at the sub-tree level ([#12731](https://github.com/remix-run/react-router/pull/12731)
    )
*   `react-router` - Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12800](https://github.com/remix-run/react-router/pull/12800)
    , [#12882](https://github.com/remix-run/react-router/pull/12882)
    )
*   `react-router` - Internal reorg to clean up some duplicated route module types ([#12799](https://github.com/remix-run/react-router/pull/12799)
    )

**Full Changelog**: [`v7.1.3...v7.1.4`](https://github.com/remix-run/react-router/compare/react-router@7.1.3...react-router@7.1.4)

[](#v713)
v7.1.3
----------------

Date: 2025-01-17

### [](#patch-changes-11)
Patch Changes

*   `@react-router/dev` - Fix `reveal` and `routes` CLI commands ([#12745](https://github.com/remix-run/react-router/pull/12745)
    )

**Full Changelog**: [`v7.1.2...v7.1.3`](https://github.com/remix-run/react-router/compare/react-router@7.1.2...react-router@7.1.3)

[](#v712)
v7.1.2
----------------

Date: 2025-01-16

### [](#patch-changes-12)
Patch Changes

*   `react-router` - Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12681](https://github.com/remix-run/react-router/pull/12681)
    )
*   `react-router` - Do not rely on `symbol` for filtering out `redirect` responses from loader data ([#12694](https://github.com/remix-run/react-router/pull/12694)
    )
    *   Previously, some projects were getting type checking errors like:
        
            error TS4058: Return type of exported function has or is using name 'redirectSymbol' from external module "node_modules/..." but cannot be named.
            
        
    *   Now that `symbol`s are not used for the `redirect` response type, these errors should no longer be present
*   `@react-router/dev` - Fix default external conditions in Vite v6 ([#12644](https://github.com/remix-run/react-router/pull/12644)
    )
    *   This fixes resolution issues with certain npm packages
*   `@react-router/dev` - Fix mismatch in prerendering html/data files when path is missing a leading slash ([#12684](https://github.com/remix-run/react-router/pull/12684)
    )
*   `@react-router/dev` - Use `module-sync` server condition when enabled in the runtime. This fixes React context mismatches (e.g. `useHref() may be used only in the context of a <Router> component.`) during development on Node 22.10.0+ when using libraries that have a peer dependency on React Router ([#12729](https://github.com/remix-run/react-router/pull/12729)
    )
*   `@react-router/dev` - Fix `react-refresh` source maps ([#12686](https://github.com/remix-run/react-router/pull/12686)
    )

**Full Changelog**: [`v7.1.1...v7.1.2`](https://github.com/remix-run/react-router/compare/react-router@7.1.1...react-router@7.1.2)

[](#v711)
v7.1.1
----------------

Date: 2024-12-23

### [](#patch-changes-13)
Patch Changes

*   `@react-router/dev` - Fix for a crash when optional args are passed to the CLI ([#12609](https://github.com/remix-run/react-router/pull/12609)
    )

**Full Changelog**: [`v7.1.0...v7.1.1`](https://github.com/remix-run/react-router/compare/react-router@7.1.0...react-router@7.1.1)

[](#v710)
v7.1.0
----------------

Date: 2024-12-20

### [](#minor-changes-5)
Minor Changes

*   Add support for Vite v6 ([#12469](https://github.com/remix-run/react-router/pull/12469)
    )

### [](#patch-changes-14)
Patch Changes

*   `react-router` - Throw unwrapped Single Fetch `redirect` to align with pre-Single Fetch behavior ([#12506](https://github.com/remix-run/react-router/pull/12506)
    )
*   `react-router` - Ignore redirects when inferring loader data types ([#12527](https://github.com/remix-run/react-router/pull/12527)
    )
*   `react-router` - Remove `<Link prefetch>` warning which suffers from false positives in a lazy route discovery world ([#12485](https://github.com/remix-run/react-router/pull/12485)
    )
*   `create-react-router` - Fix missing `fs-extra` dependency ([#12556](https://github.com/remix-run/react-router/pull/12556)
    )
*   `@react-router/dev`/`@react-router/serve` - Properly initialize `NODE_ENV` if not already set for compatibility with React 19 ([#12578](https://github.com/remix-run/react-router/pull/12578)
    )
*   `@react-router/dev` - Remove the leftover/unused `abortDelay` prop from `ServerRouter` and update the default `entry.server.tsx` to use the new `streamTimeout` value for Single Fetch ([#12478](https://github.com/remix-run/react-router/pull/12478)
    )
    *   The `abortDelay` functionality was removed in v7 as it was coupled to the `defer` implementation from Remix v2, but this removal of this prop was missed
    *   If you were still using this prop in your `entry.server` file, it's likely your app is not aborting streams as you would expect and you will need to adopt the new [`streamTimeout`](https://reactrouter.com/explanation/special-files#streamtimeout)
         value introduced with Single Fetch
*   `@react-router/fs-routes` - Throw error in `flatRoutes` if routes directory is missing ([#12407](https://github.com/remix-run/react-router/pull/12407)
    )

### [](#changes-by-package-5)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/create-react-router/CHANGELOG.md#710)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router/CHANGELOG.md#710)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-architect/CHANGELOG.md#710)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-cloudflare/CHANGELOG.md#710)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-dev/CHANGELOG.md#710)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-express/CHANGELOG.md#710)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-fs-routes/CHANGELOG.md#710)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-node/CHANGELOG.md#710)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#710)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-serve/CHANGELOG.md#710)
    

**Full Changelog**: [`v7.0.2...v7.1.0`](https://github.com/remix-run/react-router/compare/react-router@7.0.2...react-router@7.1.0)

[](#v702)
v7.0.2
----------------

Date: 2024-12-02

### [](#patch-changes-15)
Patch Changes

*   `react-router` - Temporarily only use one build in export map so packages can have a peer dependency on react router ([#12437](https://github.com/remix-run/react-router/pull/12437)
    )
*   `@react-router/dev` - Support `moduleResolution` `Node16` and `NodeNext` ([#12440](https://github.com/remix-run/react-router/pull/12440)
    )
*   `@react-router/dev` - Generate wide `matches` and `params` types for child routes ([#12397](https://github.com/remix-run/react-router/pull/12397)
    )
    *   At runtime, `matches` includes child route matches and `params` include child route path parameters
    *   But previously, we only generated types for parent routes and the current route in `matches` and `params`
    *   To align our generated types more closely to the runtime behavior, we now generate more permissive, wider types when accessing child route information

**Full Changelog**: [`v7.0.1...v7.0.2`](https://github.com/remix-run/react-router/compare/react-router@7.0.1...react-router@7.0.2)

[](#v701)
v7.0.1
----------------

Date: 2024-11-22

### [](#patch-changes-16)
Patch Changes

*   `@react-router/dev` - Ensure typegen file watcher is cleaned up when Vite dev server restarts ([#12331](https://github.com/remix-run/react-router/pull/12331)
    )
*   `@react-router/dev` - Pass route `error` to `ErrorBoundary` as a prop ([#12338](https://github.com/remix-run/react-router/pull/12338)
    )

**Full Changelog**: [`v7.0.0...v7.0.1`](https://github.com/remix-run/react-router/compare/react-router@7.0.0...react-router@7.0.1)

[](#v700)
v7.0.0
----------------

Date: 2024-11-21

### [](#breaking-changes)
Breaking Changes

#### [](#package-restructuring)
Package Restructuring

*   The `react-router-dom`, `@remix-run/react`, `@remix-run/server-runtime`, and `@remix-run/router` have been collapsed into the `react-router` package
    *   To ease migration, `react-router-dom` is still published in v7 as a re-export of everything from `react-router`
*   The `@remix-run/cloudflare-pages` and `@remix-run/cloudflare-workers` have been collapsed into `@react-router/cloudflare` package\`
*   The `react-router-dom-v5-compat` and `react-router-native` packages are removed starting with v7

#### [](#removed-adapter-re-exports)
Removed Adapter Re-exports

Remix v2 used to re-export all common `@remix-run/server-runtime` APIs through the various runtime packages (`node`, `cloudflare`, `deno`) so that you wouldn't need an additional `@remix-run/server-runtime` dependency in your `package.json`. With the collapsing of packages into `react-router`, these common APIs are now no longer re-exported through the runtime adapters. You should import all common APIs from `react-router`, and only import runtime-specific APIs from the runtime packages:

    // Runtime-specific APIs
    import { createFileSessionStorage } from "@react-router/node";
    // Runtime-agnostic APIs
    import { redirect, useLoaderData } from "react-router";
    

#### [](#removed-apis)
Removed APIs

The following APIs have been removed in React Router v7:

*   `json`
*   `defer`
*   `unstable_composeUploadHandlers`
*   `unstable_createMemoryUploadHandler`
*   `unstable_parseMultipartFormData`

#### [](#minimum-versions)
Minimum Versions

React Router v7 requires the following minimum versions:

*   `node@20`
    *   React Router no longer provides an `installGlobals` method to [polyfill](https://reactrouter.com/dev/guides/deploying/custom-node#polyfilling-fetch)
         the `fetch` API
*   `react@18`, `react-dom@18`

#### [](#adopted-future-flag-behaviors)
Adopted Future Flag Behaviors

Remix and React Router follow an [API Development Strategy](https://reactrouter.com/en/main/guides/api-development-strategy)
 leveraging "Future Flags" to avoid introducing a slew of breaking changes in a major release. Instead, breaking changes are introduced in minor releases behind a flag, allowing users to opt-in at their convenience. In the next major release, all future flag behaviors become the default behavior.

The following previously flagged behaviors are now the default in React Router v7:

*   [React Router v6 flags](https://reactrouter.com/en/v6/upgrading/future)
    *   `future.v7_relativeSplatPath`
    *   `future.v7_startTransition`
    *   `future.v7_fetcherPersist`
    *   `future.v7_normalizeFormMethod`
    *   `future.v7_partialHydration`
    *   `future.v7_skipActionStatusRevalidation`
*   [Remix v2 flags](https://remix.run/docs/en/v2/start/future-flags)
    *   `future.v3_fetcherPersist`
    *   `future.v3_relativeSplatPath`
    *   `future.v3_throwAbortReason`
    *   `future.v3_singleFetch`
    *   `future.v3_lazyRouteDiscovery`
    *   `future.v3_optimizeDeps`

#### [](#vite-compiler)
Vite Compiler

The [Remix Vite plugin](https://remix.run/docs/en/2.12.1/start/future-flags#vite-plugin)
 is the proper way to build full-stack SSR apps using React Router v7. The former `esbuild`\-based compiler is no longer available.

**Renamed `vitePlugin` and `cloudflareDevProxyVitePlugin`**

For Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved ([#11904](https://github.com/remix-run/react-router/pull/11904)
)

    -import {
    -  vitePlugin as remix,
    -  cloudflareDevProxyVitePlugin,
    -} from "@remix/dev";
    
    +import { reactRouter } from "@react-router/dev/vite";
    +import { cloudflareDevProxy } from "@react-router/dev/vite/cloudflare";
    

**Removed `manifest` option**

For Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed. The `manifest` option been superseded by the more powerful `buildEnd` hook since it's passed the `buildManifest` argument. You can still write the build manifest to disk if needed, but you'll most likely find it more convenient to write any logic depending on the build manifest within the `buildEnd` hook itself. ([#11573](https://github.com/remix-run/react-router/pull/11573)
)

If you were using the `manifest` option, you can replace it with a `buildEnd` hook that writes the manifest to disk like this:

    // react-router.config.ts
    import { type Config } from "@react-router/dev/config";
    import { writeFile } from "node:fs/promises";
    
    export default {
      async buildEnd({ buildManifest }) {
        await writeFile(
          "build/manifest.json",
          JSON.stringify(buildManifest, null, 2),
          "utf-8"
        );
      },
    } satisfies Config;
    

#### [](#exposed-router-promises)
Exposed Router Promises

Because React 19 will have first-class support for handling promises in the render pass (via `React.use` and `useAction`), we are now comfortable exposing the promises for the APIs that previously returned `undefined`:

*   `useNavigate()`
*   `useSubmit()`
*   `useFetcher().load`
*   `useFetcher().submit`
*   `useRevalidator().revalidate()`

### [](#other-notable-changes)
Other Notable Changes

#### [](#routests)
`routes.ts`

When using the React Router Vite plugin, routes are defined in `app/routes.ts`. Route config is exported via the `routes` export, conforming to the `RouteConfig` type. Route helper functions `route`, `index`, and `layout` are provided to make declarative type-safe route definitions easier.

    // app/routes.ts
    import {
      type RouteConfig,
      route,
      index,
      layout,
    } from "@react-router/dev/routes";
    
    export const routes: RouteConfig = [\
      index("./home.tsx"),\
      route("about", "./about.tsx"),\
    \
      layout("./auth/layout.tsx", [\
        route("login", "./auth/login.tsx"),\
        route("register", "./auth/register.tsx"),\
      ]),\
    \
      route("concerts", [\
        index("./concerts/home.tsx"),\
        route(":city", "./concerts/city.tsx"),\
        route("trending", "./concerts/trending.tsx"),\
      ]),\
    ];
    

For Remix consumers migrating to React Router, you can still configure file system routing within `routes.ts` using the `@react-router/fs-routes` package. A minimal route config that reproduces the default Remix setup looks like this:

    // app/routes.ts
    import { type RouteConfig } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export const routes: RouteConfig = flatRoutes();
    

If you want to migrate from file system routing to config-based routes, you can mix and match approaches by spreading the results of the async `flatRoutes` function into the array of config-based routes.

    // app/routes.ts
    import { type RouteConfig, route } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export const routes: RouteConfig = [\
      // Example config-based route:\
      route("/hello", "./routes/hello.tsx"),\
    \
      // File system routes scoped to a different directory:\
      ...(await flatRoutes({\
        rootDirectory: "fs-routes",\
      })),\
    ];
    

If you were using Remix's `routes` option to use alternative file system routing conventions, you can adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter`.

For example, if you were using [Remix v1 route conventions](https://remix.run/docs/en/1.19.3/file-conventions/routes-files)
 in Remix v2, you can combine `@react-router/remix-config-routes-adapter` with `@remix-run/v1-route-convention` to adapt this to React Router:

    // app/routes.ts
    import { type RouteConfig } from "@react-router/dev/routes";
    import { remixConfigRoutes } from "@react-router/remix-config-routes-adapter";
    import { createRoutesFromFolders } from "@remix-run/v1-route-convention";
    
    export const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {
      return createRoutesFromFolders(defineRoutes, {
        ignoredFilePatterns: ["**/.*", "**/*.css"],
      });
    });
    

Also note that, if you were using Remix's `routes` option to define config-based routes, you can also adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter` with minimal code changes. While this makes for a fast migration path, we recommend migrating any config-based routes from Remix to the new `RouteConfig` format since it's a fairly straightforward migration.

    // app/routes.ts
    -import { type RouteConfig } from "@react-router/dev/routes";
    +import { type RouteConfig, route } from "@react-router/dev/routes";
    -import { remixConfigRoutes } from "@react-router/remix-config-routes-adapter";
    
    -export const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {
    -  defineRoutes((route) => {
    -    route("/parent", "./routes/parent.tsx", () => [\
    -      route("/child", "./routes/child.tsx"),\
    -    ]);
    -  });
    -});
    +export const routes: RouteConfig = [\
    +  route("/parent", "./routes/parent.tsx", [\
    +    route("/child", "./routes/child.tsx"),\
    +  ]),\
    +];
    

#### [](#typesafety-improvements)
Typesafety improvements

React Router now generates types for each of your route modules and passes typed props to route module component exports ([#11961](https://github.com/remix-run/react-router/pull/11961)
, [#12019](https://github.com/remix-run/react-router/pull/12019)
). You can access those types by importing them from `./+types/<route filename without extension>`.

See [_How To > Route Module Type Safety_](https://reactrouter.com/dev/how-to/route-module-type-safety)
 and [_Explanations > Type Safety_](https://reactrouter.com/dev/explanation/type-safety)
 for more details.

#### [](#prerendering)
Prerendering

React Router v7 includes a new `prerender` config in the vite plugin to support SSG use-cases. This will pre-render your `.html` and `.data` files at build time and so you can serve them statically at runtime from a running server or a CDN ([#11539](https://github.com/remix-run/react-router/pull/11539)
)

    export default defineConfig({
      plugins: [\
        reactRouter({\
          async prerender({ getStaticPaths }) {\
            let slugs = await fakeGetSlugsFromCms();\
            return [\
              ...getStaticPaths(),\
              ...slugs.map((slug) => `/product/${slug}`),\
            ];\
          },\
        }),\
        tsconfigPaths(),\
      ],
    });
    
    async function fakeGetSlugsFromCms() {
      await new Promise((r) => setTimeout(r, 1000));
      return ["shirt", "hat"];
    }
    

### [](#major-changes-react-router)
Major Changes (`react-router`)

*   Remove the original `defer` implementation in favor of using raw promises via single fetch and `turbo-stream` ([#11744](https://github.com/remix-run/react-router/pull/11744)
    )
    *   This removes these exports from React Router:
        *   `defer`
        *   `AbortedDeferredError`
        *   `type TypedDeferredData`
        *   `UNSAFE_DeferredData`
        *   `UNSAFE_DEFERRED_SYMBOL`
*   Collapse packages into `react-router`([#11505](https://github.com/remix-run/react-router/pull/11505)
    )
    *   `@remix-run/router`
    *   `react-router-dom`
    *   `@remix-run/server-runtime`
    *   `@remix-run/testing`
    *   As a note, the `react-router-dom` package is maintained to ease adoption but it simply re-exports all APIs from `react-router`
*   Drop support for Node 16, React Router SSR now requires Node 18 or higher ([#11391](https://github.com/remix-run/react-router/pull/11391)
    , [#11690](https://github.com/remix-run/react-router/pull/11690)
    )
*   Remove `future.v7_startTransition` flag ([#11696](https://github.com/remix-run/react-router/pull/11696)
    )
*   Expose the underlying router promises from the following APIs for composition in React 19 APIs: ([#11521](https://github.com/remix-run/react-router/pull/11521)
    )
*   Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697)
    )
*   Imports/Exports cleanup ([#11840](https://github.com/remix-run/react-router/pull/11840)
    )
    *   Removed the following exports that were previously public API from `@remix-run/router`
        *   types
            *   `AgnosticDataIndexRouteObject`
            *   `AgnosticDataNonIndexRouteObject`
            *   `AgnosticDataRouteMatch`
            *   `AgnosticDataRouteObject`
            *   `AgnosticIndexRouteObject`
            *   `AgnosticNonIndexRouteObject`
            *   `AgnosticRouteMatch`
            *   `AgnosticRouteObject`
            *   `TrackedPromise`
            *   `unstable_AgnosticPatchRoutesOnMissFunction`
            *   `Action` -> exported as `NavigationType` via `react-router`
            *   `Router` exported as `RemixRouter` to differentiate from RR's `<Router>`
        *   API
            *   `getToPathname` (`@private`)
            *   `joinPaths` (`@private`)
            *   `normalizePathname` (`@private`)
            *   `resolveTo` (`@private`)
            *   `stripBasename` (`@private`)
            *   `createBrowserHistory` -> in favor of `createBrowserRouter`
            *   `createHashHistory` -> in favor of `createHashRouter`
            *   `createMemoryHistory` -> in favor of `createMemoryRouter`
            *   `createRouter`
            *   `createStaticHandler` -> in favor of wrapper `createStaticHandler` in RR Dom
            *   `getStaticContextFromError`
    *   Removed the following exports that were previously public API from `react-router`
        *   `Hash`
        *   `Pathname`
        *   `Search`
*   Remove `future.v7_prependBasename` from the internalized `@remix-run/router` package ([#11726](https://github.com/remix-run/react-router/pull/11726)
    )
*   Remove `future.v7_throwAbortReason` from internalized `@remix-run/router` package ([#11728](https://github.com/remix-run/react-router/pull/11728)
    )
*   Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675)
    )
*   Renamed `RemixContext` to `FrameworkContext` ([#11705](https://github.com/remix-run/react-router/pull/11705)
    )
*   Update the minimum React version to 18 ([#11689](https://github.com/remix-run/react-router/pull/11689)
    )
*   `PrefetchPageDescriptor` replaced by `PageLinkDescriptor` ([#11960](https://github.com/remix-run/react-router/pull/11960)
    )
*   Remove the `future.v7_partialHydration` flag ([#11725](https://github.com/remix-run/react-router/pull/11725)
    )
    *   This also removes the `<RouterProvider fallbackElement>` prop
        *   To migrate, move the `fallbackElement` to a `hydrateFallbackElement`/`HydrateFallback` on your root route
    *   Also worth nothing there is a related breaking changer with this future flag:
        *   Without `future.v7_partialHydration` (when using `fallbackElement`), `state.navigation` was populated during the initial load
        *   With `future.v7_partialHydration`, `state.navigation` remains in an `"idle"` state during the initial load
*   Remove `future.v7_relativeSplatPath` future flag ([#11695](https://github.com/remix-run/react-router/pull/11695)
    )
*   Remove remaining future flags ([#11820](https://github.com/remix-run/react-router/pull/11820)
    )
    *   React Router `v7_skipActionErrorRevalidation`
    *   Remix `v3_fetcherPersist`, `v3_relativeSplatPath`, `v3_throwAbortReason`
*   Rename `createRemixStub` to `createRoutesStub` ([#11692](https://github.com/remix-run/react-router/pull/11692)
    )
*   Remove `@remix-run/router` deprecated `detectErrorBoundary` option in favor of `mapRouteProperties` ([#11751](https://github.com/remix-run/react-router/pull/11751)
    )
*   Add `react-router/dom` subpath export to properly enable `react-dom` as an optional `peerDependency` ([#11851](https://github.com/remix-run/react-router/pull/11851)
    )
    *   This ensures that we don't blindly `import ReactDOM from "react-dom"` in `<RouterProvider>` in order to access `ReactDOM.flushSync()`, since that would break `createMemoryRouter` use cases in non-DOM environments
    *   DOM environments should import from `react-router/dom` to get the proper component that makes `ReactDOM.flushSync()` available:
        *   If you are using the Vite plugin, use this in your `entry.client.tsx`:
            *   `import { HydratedRouter } from 'react-router/dom'`
        *   If you are not using the Vite plugin and are manually calling `createBrowserRouter`/`createHashRouter`:
            *   `import { RouterProvider } from "react-router/dom"`
*   Remove `future.v7_fetcherPersist` flag ([#11731](https://github.com/remix-run/react-router/pull/11731)
    )
*   Allow returning `undefined` from loaders and actions ([#11680](https://github.com/remix-run/react-router/pull/11680)
    , [#12057](%5Bhttps://github.com/remix-run/react-router/pull/1205)
    )
*   Use `createRemixRouter`/`RouterProvider` in `entry.client` instead of `RemixBrowser` ([#11469](https://github.com/remix-run/react-router/pull/11469)
    )
*   Remove the deprecated `json` utility ([#12146](https://github.com/remix-run/react-router/pull/12146)
    )
    *   You can use [`Response.json`](https://developer.mozilla.org/en-US/docs/Web/API/Response/json_static)
         if you still need to construct JSON responses in your app

### [](#major-changes-react-router-1)
Major Changes (`@react-router/*`)

*   Remove `future.v3_singleFetch` flag ([#11522](https://github.com/remix-run/react-router/pull/11522)
    )
*   Drop support for Node 16 and 18, update minimum Node version to 20 ([#11690](https://github.com/remix-run/react-router/pull/11690)
    , [#12171](https://github.com/remix-run/react-router/pull/12171)
    )
    *   Remove `installGlobals()` as this should no longer be necessary
*   Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675)
    )
*   No longer re-export APIs from `react-router` through different runtime/adapter packages ([#11702](https://github.com/remix-run/react-router/pull/11702)
    )
*   For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API)
     is now required when using cookie and session APIs
    *   This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837)
        )
        *   `createCookie`
        *   `createCookieSessionStorage`
        *   `createMemorySessionStorage`
        *   `createSessionStorage`
    *   For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation](https://nodejs.org/api/webcrypto.html)
        
    *   Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
        *   `createCookieFactory`
        *   `createSessionStorageFactory`
        *   `createCookieSessionStorageFactory`
        *   `createMemorySessionStorageFactory`
*   Consolidate types previously duplicated across `@remix-run/router`, `@remix-run/server-runtime`, and `@remix-run/react` now that they all live in `react-router` ([#12177](https://github.com/remix-run/react-router/pull/12177)
    )
    *   Examples: `LoaderFunction`, `LoaderFunctionArgs`, `ActionFunction`, `ActionFunctionArgs`, `DataFunctionArgs`, `RouteManifest`, `LinksFunction`, `Route`, `EntryRoute`
    *   The `RouteManifest` type used by the "remix" code is now slightly stricter because it is using the former `@remix-run/router` `RouteManifest`
        *   `Record<string, Route> -> Record<string, Route | undefined>`
    *   Removed `AppData` type in favor of inlining `unknown` in the few locations it was used
    *   Removed `ServerRuntimeMeta*` types in favor of the `Meta*` types they were duplicated from
*   Migrate Remix v2 type generics to React Router ([#12180](https://github.com/remix-run/react-router/pull/12180)
    )
    *   These generics are provided for Remix v2 migration purposes
    *   These generics and the APIs they exist on should be considered informally deprecated in favor of the new `Route.*` types
    *   Anyone migrating from React Router v6 should probably not leverage these new generics and should migrate straight to the `Route.*` types
    *   For React Router v6 users, these generics are new and should not impact your app, with one exception
        *   `useFetcher` previously had an optional generic (used primarily by Remix v2) that expected the data type
        *   This has been updated in v7 to expect the type of the function that generates the data (i.e., `typeof loader`/`typeof action`)
        *   Therefore, you should update your usages:
            *   ❌ `useFetcher<LoaderData>()`
            *   ✅ `useFetcher<typeof loader>()`
*   Update `cookie` dependency to `^1.0.1` - please see the [release notes](https://github.com/jshttp/cookie/releases)
     for any breaking changes ([#12172](https://github.com/remix-run/react-router/pull/12172)
    )
*   `@react-router/cloudflare` - For Remix consumers migrating to React Router, all exports from `@remix-run/cloudflare-pages` are now provided for React Router consumers in the `@react-router/cloudflare` package. There is no longer a separate package for Cloudflare Pages. ([#11801](https://github.com/remix-run/react-router/pull/11801)
    )
*   `@react-router/cloudflare` - The `@remix-run/cloudflare-workers` package has been deprecated. Remix consumers migrating to React Router should use the `@react-router/cloudflare` package directly. For guidance on how to use `@react-router/cloudflare` within a Cloudflare Workers context, refer to the Cloudflare Workers template. ([#11801](https://github.com/remix-run/react-router/pull/11801)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved. ([#11904](https://github.com/remix-run/react-router/pull/11904)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router who used the Vite plugin's `buildEnd` hook, the resolved `reactRouterConfig` object no longer contains a `publicPath` property since this belongs to Vite, not React Router ([#11575](https://github.com/remix-run/react-router/pull/11575)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed ([#11573](https://github.com/remix-run/react-router/pull/11573)
    )
*   `@react-router/dev` - Update default `isbot` version to v5 and drop support for `isbot@3` ([#11770](https://github.com/remix-run/react-router/pull/11770)
    )
    *   If you have `isbot@4` or `isbot@5` in your `package.json`:
        *   You do not need to make any changes
    *   If you have `isbot@3` in your `package.json` and you have your own `entry.server.tsx` file in your repo
        *   You do not need to make any changes
        *   You can upgrade to `isbot@5` independent of the React Router v7 upgrade
    *   If you have `isbot@3` in your `package.json` and you do not have your own `entry.server.tsx` file in your repo
        *   You are using the internal default entry provided by React Router v7 and you will need to upgrade to `isbot@5` in your `package.json`
*   `@react-router/dev` - For Remix consumers migrating to React Router, Vite manifests (i.e. `.vite/manifest.json`) are now written within each build subdirectory, e.g. `build/client/.vite/manifest.json` and `build/server/.vite/manifest.json` instead of `build/.vite/client-manifest.json` and `build/.vite/server-manifest.json`. This means that the build output is now much closer to what you'd expect from a typical Vite project. ([#11573](https://github.com/remix-run/react-router/pull/11573)
    )
    *   Originally the Remix Vite plugin moved all Vite manifests to a root-level `build/.vite` directory to avoid accidentally serving them in production, particularly from the client build. This was later improved with additional logic that deleted these Vite manifest files at the end of the build process unless Vite's `build.manifest` had been enabled within the app's Vite config. This greatly reduced the risk of accidentally serving the Vite manifests in production since they're only present when explicitly asked for. As a result, we can now assume that consumers will know that they need to manage these additional files themselves, and React Router can safely generate a more standard Vite build output.

### [](#minor-changes-6)
Minor Changes

*   `react-router` - Params, loader data, and action data as props for route component exports ([#11961](https://github.com/remix-run/react-router/pull/11961)
    )
*   `react-router` - Add route module type generation ([#12019](https://github.com/remix-run/react-router/pull/12019)
    )
*   `react-router` - Remove duplicate `RouterProvider` implementations ([#11679](https://github.com/remix-run/react-router/pull/11679)
    )
*   `react-router` - Stabilize `unstable_dataStrategy` ([#11969](https://github.com/remix-run/react-router/pull/11969)
    )
*   `react-router` - Stabilize `unstable_patchRoutesOnNavigation` ([#11970](https://github.com/remix-run/react-router/pull/11970)
    )
*   `react-router` - Add prefetching support to `Link`/`NavLink` when using Remix SSR ([#11402](https://github.com/remix-run/react-router/pull/11402)
    )
*   `react-router` - Enhance `ScrollRestoration` so it can restore properly on an SSR'd document load ([#11401](https://github.com/remix-run/react-router/pull/11401)
    )
*   `@react-router/dev` - Add support for the `prerender` config in the React Router vite plugin, to support existing SSG use-cases ([#11539](https://github.com/remix-run/react-router/pull/11539)
    )
*   `@react-router/dev` - Remove internal `entry.server.spa.tsx` implementation which was not compatible with the Single Fetch async hydration approach ([#11681](https://github.com/remix-run/react-router/pull/11681)
    )
*   `@react-router/serve`: Update `express.static` configurations to support new `prerender` API ([#11547](https://github.com/remix-run/react-router/pull/11547)
    )
    *   Assets in the `build/client/assets` folder are served as before, with a 1-year immutable `Cache-Control` header
    *   Static files outside of assets, such as pre-rendered `.html` and `.data` files are not served with a specific `Cache-Control` header
    *   `.data` files are served with `Content-Type: text/x-turbo`
        *   For some reason, when adding this via `express.static`, it seems to also add a `Cache-Control: public, max-age=0` to `.data` files

### [](#patch-changes-17)
Patch Changes

*   Replace `substr` with `substring` ([#12080](https://github.com/remix-run/react-router/pull/12080)
    )
*   `react-router` - Fix redirects returned from loaders/actions using `data()` ([#12021](https://github.com/remix-run/react-router/pull/12021)
    )
*   `@react-router/dev` - Enable prerendering for resource routes ([#12200](https://github.com/remix-run/react-router/pull/12200)
    )
*   `@react-router/dev` - resolve config directory relative to flat output file structure ([#12187](https://github.com/remix-run/react-router/pull/12187)
    )

### [](#changes-by-package-6)
Changes by Package

*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router/CHANGELOG.md#700)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-architect/CHANGELOG.md#700)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-cloudflare/CHANGELOG.md#700)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-dev/CHANGELOG.md#700)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-express/CHANGELOG.md#700)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-fs-routes/CHANGELOG.md#700)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-node/CHANGELOG.md#700)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#700)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-serve/CHANGELOG.md#700)
    

**Full Changelog**: [`v6.28.0...v7.0.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@7.0.0)

[](#react-router-v6-releases)
React Router v6 Releases
======================================================

[](#v6300)
v6.30.0
------------------

Date: 2025-02-27

### [](#minor-changes-7)
Minor Changes

*   Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13109](https://github.com/remix-run/react-router/pull/13109)
    )

### [](#patch-changes-18)
Patch Changes

*   Fix regression introduced in `6.29.0` via [#12169](https://github.com/remix-run/react-router/pull/12169)
     that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#13108](https://github.com/remix-run/react-router/pull/13108)
    )

**Full Changelog**: [`v6.29.0...v6.30.0`](https://github.com/remix-run/react-router/compare/react-router@6.29.0...react-router@6.30.0)

[](#v6290)
v6.29.0
------------------

Date: 2025-01-30

### [](#minor-changes-8)
Minor Changes

*   Provide the request `signal` as a parameter to `patchRoutesOnNavigation` ([#12900](https://github.com/remix-run/react-router/pull/12900)
    )
    *   This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted

### [](#patch-changes-19)
Patch Changes

*   Do not log v7 deprecation warnings in production builds ([#12794](https://github.com/remix-run/react-router/pull/12794)
    )
*   Properly bubble headers when throwing a `data()` result ([#12845](https://github.com/remix-run/react-router/pull/12845)
    )
*   Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12169](https://github.com/remix-run/react-router/pull/12169)
    )
*   Strip search parameters from `patchRoutesOnNavigation` `path` param for fetcher calls ([#12899](https://github.com/remix-run/react-router/pull/12899)
    )

**Full Changelog**: [`v6.28.2...v6.29.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.2...react-router@6.29.0)

[](#v6282)
v6.28.2
------------------

Date: 2025-01-16

### [](#patch-changes-20)
Patch Changes

*   Fix manual fetcher `key` usage when not opted into `future.v7_fetcherPersist` ([#12674](https://github.com/remix-run/react-router/pull/12674)
    )
*   Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12674](https://github.com/remix-run/react-router/pull/12674)
    )

**Full Changelog**: [`v6.28.1...v6.28.2`](https://github.com/remix-run/react-router/compare/react-router@6.28.1...react-router@6.28.2)

[](#v6281)
v6.28.1
------------------

Date: 2024-12-20

### [](#patch-changes-21)
Patch Changes

*   Allow users to opt out of v7 deprecation warnings by setting flags to `false` ([#12441](https://github.com/remix-run/react-router/pull/12441)
    )

**Full Changelog**: [`v6.28.0...v6.28.1`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@6.28.1)

[](#v6280)
v6.28.0
------------------

Date: 2024-11-06

### [](#whats-changed-3)
What's Changed

*   In preparation for v7 we've added deprecation warnings for any future flags that you have not yet opted into. Please use the flags to better prepare for eventually upgrading to v7.

### [](#minor-changes-9)
Minor Changes

*   Log deprecation warnings for v7 flags ([#11750](https://github.com/remix-run/react-router/pull/11750)
    )
    *   Add deprecation warnings to `json`/`defer` in favor of returning raw objects
        *   These methods will be removed in React Router v7

### [](#patch-changes-22)
Patch Changes

*   Update JSDoc URLs for new website structure (add /v6/ segment) ([#12141](https://github.com/remix-run/react-router/pull/12141)
    )

**Full Changelog**: [`v6.27.0...v6.28.0`](https://github.com/remix-run/react-router/compare/react-router@6.27.0...react-router@6.28.0)

[](#v6270)
v6.27.0
------------------

Date: 2024-10-11

### [](#whats-changed-4)
What's Changed

#### [](#stabilized-apis)
Stabilized APIs

This release stabilizes a handful of "unstable" APIs in preparation for the [pending](https://x.com/remix_run/status/1841926034868077009)
 React Router v7 release (see [these](https://remix.run/blog/merging-remix-and-react-router)
 [posts](https://remix.run/blog/incremental-path-to-react-19)
 for more info):

*   `unstable_dataStrategy` → `dataStrategy` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optsdatastrategy)
    )
*   `unstable_patchRoutesOnNavigation` → `patchRoutesOnNavigation` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optspatchroutesonnavigation)
    )
*   `unstable_flushSync` → `flushSync` (`useSubmit`, `fetcher.load`, `fetcher.submit`) ([Docs](https://reactrouter.com/v6/hooks/use-submit#optionsflushsync)
    )
*   `unstable_viewTransition` → `viewTransition` (`<Link>`, `<Form>`, `useNavigate`, `useSubmit`) ([Docs](https://reactrouter.com/v6/components/link#viewtransition)
    )

### [](#minor-changes-10)
Minor Changes

*   Stabilize the `unstable_flushSync` option for navigations and fetchers ([#11989](https://github.com/remix-run/react-router/pull/11989)
    )
*   Stabilize the `unstable_viewTransition` option for navigations and the corresponding `unstable_useViewTransitionState` hook ([#11989](https://github.com/remix-run/react-router/pull/11989)
    )
*   Stabilize `unstable_dataStrategy` ([#11974](https://github.com/remix-run/react-router/pull/11974)
    )
*   Stabilize `unstable_patchRoutesOnNavigation` ([#11973](https://github.com/remix-run/react-router/pull/11973)
    )
    *   Add new `PatchRoutesOnNavigationFunctionArgs` type for convenience ([#11967](https://github.com/remix-run/react-router/pull/11967)
        )

### [](#patch-changes-23)
Patch Changes

*   Fix bug when submitting to the current contextual route (parent route with an index child) when an `?index` param already exists from a prior submission ([#12003](https://github.com/remix-run/react-router/pull/12003)
    )
*   Fix `useFormAction` bug - when removing `?index` param it would not keep other non-Remix `index` params ([#12003](https://github.com/remix-run/react-router/pull/12003)
    )
*   Fix bug with fetchers not persisting `preventScrollReset` through redirects during concurrent fetches ([#11999](https://github.com/remix-run/react-router/pull/11999)
    )
*   Avoid unnecessary `console.error` on fetcher abort due to back-to-back revalidation calls ([#12050](https://github.com/remix-run/react-router/pull/12050)
    )
*   Fix bugs with `partialHydration` when hydrating with errors ([#12070](https://github.com/remix-run/react-router/pull/12070)
    )
*   Remove internal cache to fix issues with interrupted `patchRoutesOnNavigation` calls ([#12055](https://github.com/remix-run/react-router/pull/12055)
    )
    *   ⚠️ This may be a breaking change if you were relying on this behavior in the `unstable_` API
    *   We used to cache in-progress calls to `patchRoutesOnNavigation` internally so that multiple navigations with the same start/end would only execute the function once and use the same promise
    *   However, this approach was at odds with `patch` short circuiting if a navigation was interrupted (and the `request.signal` aborted) since the first invocation's `patch` would no-op
    *   This cache also made some assumptions as to what a valid cache key might be - and is oblivious to any other application-state changes that may have occurred
    *   So, the cache has been removed because in _most_ cases, repeated calls to something like `import()` for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userland
*   Remove internal `discoveredRoutes` FIFO queue from `unstable_patchRoutesOnNavigation` ([#11977](https://github.com/remix-run/react-router/pull/11977)
    )
    *   ⚠️ This may be a breaking change if you were relying on this behavior in the `unstable_` API
    *   This was originally implemented as an optimization but it proved to be a bit too limiting
    *   If you need this optimization you can implement your own cache inside `patchRoutesOnNavigation`
*   Fix types for `RouteObject` within `PatchRoutesOnNavigationFunction`'s `patch` method so it doesn't expect agnostic route objects passed to `patch` ([#11967](https://github.com/remix-run/react-router/pull/11967)
    )
*   Expose errors thrown from `patchRoutesOnNavigation` directly to `useRouteError` instead of wrapping them in a 400 `ErrorResponse` instance ([#12111](https://github.com/remix-run/react-router/pull/12111)
    )

**Full Changelog**: [`v6.26.2...v6.27.0`](https://github.com/remix-run/react-router/compare/react-router@6.26.2...react-router@6.27.0)

[](#v6262)
v6.26.2
------------------

Date: 2024-09-09

### [](#patch-changes-24)
Patch Changes

*   Update the `unstable_dataStrategy` API to allow for more advanced implementations ([#11943](https://github.com/remix-run/react-router/pull/11943)
    )
    *   ⚠️ If you have already adopted `unstable_dataStrategy`, please review carefully as this includes breaking changes to this API
    *   Rename `unstable_HandlerResult` to `unstable_DataStrategyResult`
    *   Change the return signature of `unstable_dataStrategy` from a parallel array of `unstable_DataStrategyResult[]` (parallel to `matches`) to a key/value object of `routeId => unstable_DataStrategyResult`
        *   This allows more advanced control over revalidation behavior because you can opt-into or out-of revalidating data that may not have been revalidated by default (via `match.shouldLoad`)
    *   You should now return/throw a result from your `handlerOverride` instead of returning a `DataStrategyResult`
        *   The return value (or thrown error) from your `handlerOverride` will be wrapped up into a `DataStrategyResult` and returned fromm `match.resolve`
        *   Therefore, if you are aggregating the results of `match.resolve()` into a final results object you should not need to think about the `DataStrategyResult` type
        *   If you are manually filling your results object from within your `handlerOverride`, then you will need to assign a `DataStrategyResult` as the value so React Router knows if it's a successful execution or an error (see examples in the documentation for details)
    *   Added a new `fetcherKey` parameter to `unstable_dataStrategy` to allow differentiation from navigational and fetcher calls
*   Preserve opted-in view transitions through redirects ([#11925](https://github.com/remix-run/react-router/pull/11925)
    )
*   Preserve pending view transitions through a router revalidation call ([#11917](https://github.com/remix-run/react-router/pull/11917)
    )
*   Fix blocker usage when `blocker.proceed` is called quickly/synchronously ([#11930](https://github.com/remix-run/react-router/pull/11930)
    )

**Full Changelog**: [`v6.26.1...v6.26.2`](https://github.com/remix-run/react-router/compare/react-router@6.26.1...react-router@6.26.2)

[](#v6261)
v6.26.1
------------------

Date: 2024-08-15

### [](#patch-changes-25)
Patch Changes

*   Rename `unstable_patchRoutesOnMiss` to `unstable_patchRoutesOnNavigation` to match new behavior ([#11888](https://github.com/remix-run/react-router/pull/11888)
    )
*   Update `unstable_patchRoutesOnNavigation` logic so that we call the method when we match routes with dynamic param or splat segments in case there exists a higher-scoring static route that we've not yet discovered ([#11883](https://github.com/remix-run/react-router/pull/11883)
    )
    *   We also now leverage an internal FIFO queue of previous paths we've already called `unstable_patchRoutesOnNavigation` against so that we don't re-call on subsequent navigations to the same path

**Full Changelog**: [`v6.26.0...v6.26.1`](https://github.com/remix-run/react-router/compare/react-router@6.26.0...react-router@6.26.1)

[](#v6260)
v6.26.0
------------------

Date: 2024-08-01

### [](#minor-changes-11)
Minor Changes

*   Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://github.com/remix-run/react-router/pull/11811)
    )
*   Add a new `unstable_data()` API for usage with Remix Single Fetch ([#11836](https://github.com/remix-run/react-router/pull/11836)
    )
    *   This API is not intended for direct usage in React Router SPA applications
    *   It is primarily intended for usage with `createStaticHandler.query()` to allow loaders/actions to return arbitrary data along with custom `status`/`headers` without forcing the serialization of data into a `Response` instance
    *   This allows for more advanced serialization tactics via `unstable_dataStrategy` such as serializing via `turbo-stream` in Remix Single Fetch
    *   ⚠️ This removes the `status` field from `HandlerResult`
        *   If you need to return a specific `status` from `unstable_dataStrategy` you should instead do so via `unstable_data()`

### [](#patch-changes-26)
Patch Changes

*   Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations ([#11839](https://github.com/remix-run/react-router/pull/11839)
    )
*   Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838)
    )
    *   During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components

**Full Changelog**: [`v6.25.1...v6.26.0`](https://github.com/remix-run/react-router/compare/react-router@6.25.1...react-router@6.26.0)

[](#v6251)
v6.25.1
------------------

Date: 2024-07-17

### [](#patch-changes-27)
Patch Changes

*   Memoize some `RouterProvider` internals to reduce unnecessary re-renders ([#11803](https://github.com/remix-run/react-router/pull/11803)
    )

**Full Changelog**: [`v6.25.0...v6.25.1`](https://github.com/remix-run/react-router/compare/react-router@6.25.0...react-router@6.25.1)

[](#v6250)
v6.25.0
------------------

Date: 2024-07-16

### [](#whats-changed-5)
What's Changed

#### [](#stabilized-v7_skipactionerrorrevalidation)
Stabilized `v7_skipActionErrorRevalidation`

This release stabilizes the `future.unstable_skipActionErrorRevalidation` flag into [`future.v7_skipActionErrorRevalidation`](https://reactrouter.com/v6/upgrading/future#v7_skipactionstatusrevalidation)
 in preparation for the upcoming React Router v7 release.

*   When this flag is enabled, actions that return/throw a `4xx/5xx` `Response` will not trigger a revalidation by default
*   This also stabilizes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus`

### [](#minor-changes-12)
Minor Changes

*   Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769)
    )

### [](#patch-changes-28)
Patch Changes

*   Fix regression and properly decode paths inside `useMatch` so matches/params reflect decoded params ([#11789](https://github.com/remix-run/react-router/pull/11789)
    )
*   Fix bubbling of errors thrown from `unstable_patchRoutesOnMiss` ([#11786](https://github.com/remix-run/react-router/pull/11786)
    )
*   Fix hydration in SSR apps using `unstable_patchRoutesOnMiss` that matched a splat route on the server ([#11790](https://github.com/remix-run/react-router/pull/11790)
    )

**Full Changelog**: [`v6.24.1...v6.25.0`](https://github.com/remix-run/react-router/compare/react-router@6.24.1...react-router@6.25.0)

[](#v6241)
v6.24.1
------------------

Date: 2024-07-03

### [](#patch-changes-29)
Patch Changes

*   Remove `polyfill.io` reference from warning message because the domain was sold and has since been determined to serve malware ([#11741](https://github.com/remix-run/react-router/pull/11741)
    )
    *   See [https://sansec.io/research/polyfill-supply-chain-attack](https://sansec.io/research/polyfill-supply-chain-attack)
        
*   Export `NavLinkRenderProps` type for easier typing of custom `NavLink` callback ([#11553](https://github.com/remix-run/react-router/pull/11553)
    )
*   When using `future.v7_relativeSplatPath`, properly resolve relative paths in splat routes that are children of pathless routes ([#11633](https://github.com/remix-run/react-router/pull/11633)
    )
*   Fog of War (unstable): Trigger a new `router.routes` identity/reflow during route patching ([#11740](https://github.com/remix-run/react-router/pull/11740)
    )
*   Fog of War (unstable): Fix initial matching when a splat route matches ([#11759](https://github.com/remix-run/react-router/pull/11759)
    )

**Full Changelog**: [`v6.24.0...v6.24.1`](https://github.com/remix-run/react-router/compare/react-router@6.24.0...react-router@6.24.1)

[](#v6240)
v6.24.0
------------------

Date: 2024-06-24

### [](#whats-changed-6)
What's Changed

#### [](#lazy-route-discovery-aka-fog-of-war)
Lazy Route Discovery (a.k.a. "Fog of War")

We're really excited to release our new API for "Lazy Route Discovery" in `v6.24.0`! For some background information, please check out the original [RFC](https://github.com/remix-run/react-router/discussions/11113)
. The **tl;dr;** is that ever since we introduced the Data APIs in v6.4 via `<RouterProvider>`, we've been a little bummed that one of the tradeoffs was the lack of a compelling code-splitting story mirroring what we had in the `<BrowserRouter>`/`<Routes>` apps. We took a baby-step towards improving that story with `route.lazy` in `v6.9.0`, but with `v6.24.0` we've gone the rest of the way.

With "Fog of War", you can now load portions of the route tree lazily via the new `unstable_patchRoutesOnMiss` option passed to `createBrowserRouter` (and it's memory/hash counterparts). This gives you a way to hook into spots where React Router is unable to match a given path and patch new routes into the route tree during the navigation (or fetcher call).

Here's a very small example, but please refer to the [documentation](https://reactrouter.com/v6/routers/create-browser-router#optsunstable_patchroutesonmiss)
 for more information and use cases:

    const router = createBrowserRouter(
      [\
        {\
          id: "root",\
          path: "/",\
          Component: RootComponent,\
        },\
      ],
      {
        async unstable_patchRoutesOnMiss({ path, patch }) {
          if (path === "/a") {
            // Load the `a` route (`{ path: 'a', Component: A }`)
            let route = await getARoute();
            // Patch the `a` route in as a new child of the `root` route
            patch("root", [route]);
          }
        },
      }
    );
    

### [](#minor-changes-13)
Minor Changes

*   Add support for Lazy Route Discovery (a.k.a. "Fog of War") ([#11626](https://github.com/remix-run/react-router/pull/11626)
    )

### [](#patch-changes-30)
Patch Changes

*   Fix `fetcher.submit` types - remove incorrect `navigate`/`fetcherKey`/`unstable_viewTransition` options because they are only relevant for `useSubmit` ([#11631](https://github.com/remix-run/react-router/pull/11631)
    )
*   Allow falsy `location.state` values passed to `<StaticRouter>` ([#11495](https://github.com/remix-run/react-router/pull/11495)
    )

**Full Changelog**: [`v6.23.1...v6.24.0`](https://github.com/remix-run/react-router/compare/react-router@6.23.1...react-router@6.24.0)

[](#v6231)
v6.23.1
------------------

Date: 2024-05-10

### [](#patch-changes-31)
Patch Changes

*   Allow `undefined` to be resolved through `<Await>` ([#11513](https://github.com/remix-run/react-router/pull/11513)
    )
*   Add defensive `document` check when checking for `document.startViewTransition` availability ([#11544](https://github.com/remix-run/react-router/pull/11544)
    )
*   Change the `react-router-dom/server` import back to `react-router-dom` instead of `index.ts` ([#11514](https://github.com/remix-run/react-router/pull/11514)
    )
*   `@remix-run/router` - Support `unstable_dataStrategy` on `staticHandler.queryRoute` ([#11515](https://github.com/remix-run/react-router/pull/11515)
    )

**Full Changelog**: [`v6.23.0...v6.23.1`](https://github.com/remix-run/react-router/compare/react-router@6.23.0...react-router@6.23.1)

[](#v6230)
v6.23.0
------------------

Date: 2024-04-23

### [](#whats-changed-7)
What's Changed

#### [](#data-strategy-unstable)
Data Strategy (unstable)

The new `unstable_dataStrategy` API is a low-level API designed for advanced use-cases where you need to take control over the data strategy for your `loader`/`action` functions. The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix ["Single Fetch"](https://remix.run/docs/guides/single-fetch)
, user-land middleware/context APIs, automatic loader caching, and more. Please see the [docs](https://reactrouter.com/v6/routers/create-browser-router#unstable_datastrategy)
 for more information.

**Note:** This is a low-level API intended for advanced use-cases. This overrides React Router's internal handling of `loader`/`action` execution, and if done incorrectly will break your app code. Please use with caution and perform the appropriate testing.

#### [](#skip-action-error-revalidation-unstable)
Skip Action Error Revalidation (unstable)

Currently, all active `loader`'s revalidate after any `action` submission, regardless of the `action` result. However, in the majority of cases a `4xx`/`5xx` response from an `action` means that no data was actually changed and the revalidation is unnecessary. We've introduced a new `future.unstable_skipActionErrorRevalidation` flag that changes the behavior here, and we plan to make this the default in future version of React Router.

With this flag enabled, `action`'s that return/throw a `4xx`/`5xx` response status will no longer automatically revalidate. If you need to revalidate after a `4xx`/`5xx` result with this flag enabled, you can still do that via returning `true` from `shouldRevalidate` - which now also receives a new `unstable_actionStatus` argument alongside `actionResult` so you can make decision based on the status of the `action` response without having to encode it into the action data.

### [](#minor-changes-14)
Minor Changes

*   Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098)
    , [#11377](https://github.com/remix-run/react-router/pull/11377)
    )
*   `@remix-run/router` - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098)
    )
*   `@remix-run/router` - SSR: Added a new `skipLoaderErrorBubbling` options to the `staticHandler.query` method to disable error bubbling by the static handler for use in Remix's Single Fetch implementation ([#11098](https://github.com/remix-run/react-router/pull/11098)
    , ([#11377](https://github.com/remix-run/react-router/pull/11377)
    ))

**Full Changelog**: [`v6.22.3...v6.23.0`](https://github.com/remix-run/react-router/compare/react-router@6.22.3...react-router@6.23.0)

[](#v6223)
v6.22.3
------------------

Date: 2024-03-07

### [](#patch-changes-32)
Patch Changes

*   Fix a `future.v7_partialHydration` bug that would re-run loaders below the boundary on hydration if SSR loader errors bubbled to a parent boundary ([#11324](https://github.com/remix-run/react-router/pull/11324)
    )
*   Fix a `future.v7_partialHydration` bug that would consider the router uninitialized if a route did not have a loader ([#11325](https://github.com/remix-run/react-router/pull/11325)
    )

**Full Changelog**: [`v6.22.2...v6.22.3`](https://github.com/remix-run/react-router/compare/react-router@6.22.2...react-router@6.22.3)

[](#v6222)
v6.22.2
------------------

Date: 2024-02-28

### [](#patch-changes-33)
Patch Changes

*   Preserve hydrated errors during partial hydration runs ([#11305](https://github.com/remix-run/react-router/pull/11305)
    )

**Full Changelog**: [`v6.22.1...v6.22.2`](https://github.com/remix-run/react-router/compare/react-router@6.22.1...react-router@6.22.2)

[](#v6221)
v6.22.1
------------------

Date: 2024-02-16

### [](#patch-changes-34)
Patch Changes

*   Fix encoding/decoding issues with pre-encoded dynamic parameter values ([#11199](https://github.com/remix-run/react-router/pull/11199)
    )

**Full Changelog**: [`v6.22.0...v6.22.1`](https://github.com/remix-run/react-router/compare/react-router@6.22.0...react-router@6.22.1)

[](#v6220)
v6.22.0
------------------

Date: 2024-02-01

### [](#whats-changed-8)
What's Changed

#### [](#core-web-vitals-technology-report-flag)
Core Web Vitals Technology Report Flag

In 2021, the HTTP Archive launched the [Core Web Vitals Technology Report dashboard](https://discuss.httparchive.org/t/new-dashboard-the-core-web-vitals-technology-report/2178)
:

> By combining the powers of real-user experiences in the Chrome UX Report 26 (CrUX) dataset with web technology detections in HTTP Archive 30, we can get a glimpse into how architectural decisions like choices of CMS platform or JavaScript framework play a role in sites’ CWV performance.

They use a tool called [`wappalyzer`](https://github.com/HTTPArchive/wappalyzer)
 to identify what technologies a given website is using by looking for certain scripts, global JS variables, or other identifying characteristics. For example, for Remix applications, they [look for the global `__remixContext`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L1328)
 variable to identify that a website is using Remix.

It was brought to our attention that React Router was unable to be reliably identified because there are no identifying global aspects. They are currently [looking for external scripts with `react-router`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L637)
 in the name. This will identify sites using React Router from a CDN such as `unpkg` - but it will miss the **vast** majority of sites that are installing React Router from the npm registry and bundling it into their JS files. This results in [drastically under-reporting](https://lookerstudio.google.com/s/pixHkNmGbN4)
 the usage of React Router on the web.

Starting with version `6.22.0`, sites using `react-router-dom` will begin adding a `window.__reactRouterVersion` variable that will be set to a string value of the SemVer major version number (i.e., `window.__reactRouterVersion = "6";`) so that they can be properly identified.

### [](#minor-changes-15)
Minor Changes

*   Include a `window.__reactRouterVersion` for CWV Report detection ([#11222](https://github.com/remix-run/react-router/pull/11222)
    )
*   Add a `createStaticHandler` `future.v7_throwAbortReason` flag to throw `request.signal.reason` (defaults to a `DOMException`) when a request is aborted instead of an `Error` such as `new Error("query() call aborted: GET /path")` ([#11104](https://github.com/remix-run/react-router/pull/11104)
    )
    *   Please note that `DOMException` was added in Node v17 so you will not get a `DOMException` on Node 16 and below.

### [](#patch-changes-35)
Patch Changes

*   Respect the `ErrorResponse` status code if passed to `getStaticContextFormError` ([#11213](https://github.com/remix-run/react-router/pull/11213)
    )

**Full Changelog**: [`v6.21.3...v6.22.0`](https://github.com/remix-run/react-router/compare/react-router@6.21.3...react-router@6.22.0)

[](#v6213)
v6.21.3
------------------

Date: 2024-01-18

### [](#patch-changes-36)
Patch Changes

*   Fix `NavLink` `isPending` when a `basename` is used ([#11195](https://github.com/remix-run/react-router/pull/11195)
    )
*   Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://github.com/remix-run/react-router/pull/11187)
    )

**Full Changelog**: [`v6.21.2...v6.21.3`](https://github.com/remix-run/react-router/compare/react-router@6.21.2...react-router@6.21.3)

[](#v6212)
v6.21.2
------------------

Date: 2024-01-11

### [](#patch-changes-37)
Patch Changes

*   Leverage `useId` for internal fetcher keys when available ([#11166](https://github.com/remix-run/react-router/pull/11166)
    )
*   Fix bug where dashes were not picked up in dynamic parameter names ([#11160](https://github.com/remix-run/react-router/pull/11160)
    )
*   Do not attempt to deserialize empty JSON responses ([#11164](https://github.com/remix-run/react-router/pull/11164)
    )

**Full Changelog**: [`v6.21.1...v6.21.2`](https://github.com/remix-run/react-router/compare/react-router@6.21.1...react-router@6.21.2)

[](#v6211)
v6.21.1
------------------

Date: 2023-12-21

### [](#patch-changes-38)
Patch Changes

*   Fix bug with `route.lazy` not working correctly on initial SPA load when `v7_partialHydration` is specified ([#11121](https://github.com/remix-run/react-router/pull/11121)
    )
*   Fix bug preventing revalidation from occurring for persisted fetchers unmounted during the `submitting` phase ([#11102](https://github.com/remix-run/react-router/pull/11102)
    )
*   De-dup relative path logic in `resolveTo` ([#11097](https://github.com/remix-run/react-router/pull/11097)
    )

**Full Changelog**: [`v6.21.0...v6.21.1`](https://github.com/remix-run/react-router/compare/react-router@6.21.0...react-router@6.21.1)

[](#v6210)
v6.21.0
------------------

Date: 2023-12-13

### [](#whats-changed-9)
What's Changed

#### [](#futurev7_relativesplatpath)
`future.v7_relativeSplatPath`

We fixed a splat route path-resolution bug in `6.19.0`, but later determined a large number of applications were relying on the buggy behavior, so we reverted the fix in `6.20.1` (see [#10983](https://github.com/remix-run/react-router/issues/10983)
, [#11052](https://github.com/remix-run/react-router/issues/11052)
, [#11078](https://github.com/remix-run/react-router/issues/11078)
).

The buggy behavior is that the default behavior when resolving relative paths inside a splat route would _ignore_ any splat (`*`) portion of the current route path. When the future flag is enabled, splat portions are included in relative path logic within splat routes.

For more information, please refer to the [`useResolvedPath` docs](https://reactrouter.com/v6/hooks/use-resolved-path#splat-paths)
 and/or the [detailed changelog entry](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md#6210)
.

#### [](#partial-hydration)
Partial Hydration

We added a new `future.v7_partialHydration` future flag for the `@remix-run/router` that enables partial hydration of a data router when Server-Side Rendering. This allows you to provide `hydrationData.loaderData` that has values for _some_ initially matched route loaders, but not all. When this flag is enabled, the router will call `loader` functions for routes that do not have hydration loader data during `router.initialize()`, and it will render down to the deepest provided `HydrateFallback` (up to the first route without hydration data) while it executes the unhydrated routes. ([#11033](https://github.com/remix-run/react-router/pull/11033)
)

### [](#minor-changes-16)
Minor Changes

*   Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087)
    )
*   Add a new `future.v7_partialHydration` future flag that enables partial hydration of a data router when Server-Side Rendering ([#11033](https://github.com/remix-run/react-router/pull/11033)
    )

### [](#patch-changes-39)
Patch Changes

*   Properly handle falsy error values in `ErrorBoundary`'s ([#11071](https://github.com/remix-run/react-router/pull/11071)
    )
*   Catch and bubble errors thrown when trying to unwrap responses from `loader`/`action` functions ([#11061](https://github.com/remix-run/react-router/pull/11061)
    )
*   Fix `relative="path"` issue when rendering `Link`/`NavLink` outside of matched routes ([#11062](https://github.com/remix-run/react-router/pull/11062)
    )

**Full Changelog**: [`v6.20.1...v6.21.0`](https://github.com/remix-run/react-router/compare/react-router@6.20.1...react-router@6.21.0)

[](#v6201)
v6.20.1
------------------

Date: 2023-12-01

### [](#patch-changes-40)
Patch Changes

*   Revert the `useResolvedPath` fix for splat routes due to a large number of applications that were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
    ) ([#11078](https://github.com/remix-run/react-router/pull/11078)
    )
    *   We plan to re-introduce this fix behind a future flag in the next minor version (see [this comment](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
        )
    *   This fix was included in versions `6.19.0` and `6.20.0`. If you are upgrading from `6.18.0` or earlier, you would not have been impacted by this fix.

**Full Changelog**: [`v6.20.0...v6.20.1`](https://github.com/remix-run/react-router/compare/react-router@6.20.0...react-router@6.20.1)

[](#v6200)
v6.20.0
------------------

Date: 2023-11-22

> \[!WARNING\] Please use version `6.20.1` or later instead of `6.20.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#11045](https://github.com/remix-run/react-router/pull/11045)
> ). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
>  for more details.

### [](#minor-changes-17)
Minor Changes

*   Export the `PathParam` type from the public API ([#10719](https://github.com/remix-run/react-router/pull/10719)
    )

### [](#patch-changes-41)
Patch Changes

*   Do not revalidate unmounted fetchers when `v7_fetcherPersist` is enabled ([#11044](https://github.com/remix-run/react-router/pull/11044)
    )
*   Fix bug with `resolveTo` path resolution in splat routes ([#11045](https://github.com/remix-run/react-router/pull/11045)
    )
    *   This is a follow up to [#10983](https://github.com/remix-run/react-router/pull/10983)
         to handle the few other code paths using `getPathContributingMatches`
    *   This removes the `UNSAFE_getPathContributingMatches` export from `@remix-run/router` since we no longer need this in the `react-router`/`react-router-dom` layers

**Full Changelog**: [`v6.19.0...v6.20.0`](https://github.com/remix-run/react-router/compare/react-router@6.19.0...react-router@6.20.0)

[](#v6190)
v6.19.0
------------------

Date: 2023-11-16

> \[!WARNING\] Please use version `6.20.1` or later instead of `6.19.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#10983](https://github.com/remix-run/react-router/pull/10983)
> ). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
>  for more details.

### [](#whats-changed-10)
What's Changed

#### [](#unstable_flushsync-api)
`unstable_flushSync` API

This release brings a new `unstable_flushSync` option to the imperative APIs (`useSubmit`, `useNavigate`, `fetcher.submit`, `fetcher.load`) to let users opt-into synchronous DOM updates for pending/optimistic UI.

    function handleClick() {
      submit(data, { flushSync: true });
      // Everything is flushed to the DOM so you can focus/scroll to your pending/optimistic UI
      setFocusAndOrScrollToNewlyAddedThing();
    }
    

### [](#minor-changes-18)
Minor Changes

*   Add `unstable_flushSync` option to `useNavigate`/`useSubmit`/`fetcher.load`/`fetcher.submit` to opt-out of `React.startTransition` and into `ReactDOM.flushSync` for state updates ([#11005](https://github.com/remix-run/react-router/pull/11005)
    )
*   Remove the `unstable_` prefix from the [`useBlocker`](https://reactrouter.com/v6/hooks/use-blocker)
     hook as it's been in use for enough time that we are confident in the API ([#10991](https://github.com/remix-run/react-router/pull/10991)
    )
    *   We do not plan to remove the prefix from `unstable_usePrompt` due to differences in how browsers handle `window.confirm` that prevent React Router from guaranteeing consistent/correct behavior

### [](#patch-changes-42)
Patch Changes

*   Fix `useActionData` so it returns proper contextual action data and not _any_ action data in the tree ([#11023](https://github.com/remix-run/react-router/pull/11023)
    )
    
*   Fix bug in `useResolvedPath` that would cause `useResolvedPath(".")` in a splat route to lose the splat portion of the URL path. ([#10983](https://github.com/remix-run/react-router/pull/10983)
    )
    
    *   ⚠️ This fixes a quite long-standing bug specifically for `"."` paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via `"."` inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.
*   Fix issue where a changing fetcher `key` in a `useFetcher` that remains mounted wasn't getting picked up ([#11009](https://github.com/remix-run/react-router/pull/11009)
    )
    
*   Fix `useFormAction` which was incorrectly inheriting the `?index` query param from child route `action` submissions ([#11025](https://github.com/remix-run/react-router/pull/11025)
    )
    
*   Fix `NavLink` `active` logic when `to` location has a trailing slash ([#10734](https://github.com/remix-run/react-router/pull/10734)
    )
    
*   Fix types so `unstable_usePrompt` can accept a `BlockerFunction` in addition to a `boolean` ([#10991](https://github.com/remix-run/react-router/pull/10991)
    )
    
*   Fix `relative="path"` bug where relative path calculations started from the full location pathname, instead of from the current contextual route pathname. ([#11006](https://github.com/remix-run/react-router/pull/11006)
    )
    
        <Route path="/a">
          <Route path="/b" element={<Component />}>
            <Route path="/c" />
          </Route>
        </Route>;
        
        function Component() {
          return (
            <>
              {/* This is now correctly relative to /a/b, not /a/b/c */}
              <Link to=".." relative="path" />
              <Outlet />
            </>
          );
        }
        
    

**Full Changelog**: [`6.18.0...6.19.0`](https://github.com/remix-run/react-router/compare/react-router@6.18.0...react-router@6.19.0)

[](#v6180)
v6.18.0
------------------

Date: 2023-10-31

### [](#whats-changed-11)
What's Changed

#### [](#new-fetcher-apis)
New Fetcher APIs

Per this [RFC](https://github.com/remix-run/remix/discussions/7698)
, we've introduced some new APIs that give you more granular control over your fetcher behaviors.

*   You may now specify your own fetcher identifier via `useFetcher({ key: string })`, which allows you to access the same fetcher instance from different components in your application without prop-drilling
*   Fetcher keys are now exposed on the fetchers returned from `useFetchers` so that they can be looked up by `key`
*   `Form` and `useSubmit` now support optional `navigate`/`fetcherKey` props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified `key`
    *   `<Form method="post" navigate={false} fetcherKey="my-key">`
    *   `submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })`
    *   Invoking a fetcher in this way is ephemeral and stateless
    *   If you need to access the state of one of these fetchers, you will need to leverage `useFetchers()` or `useFetcher({ key })` to look it up elsewhere

#### [](#persistence-future-flag-futurev7_fetcherpersist)
Persistence Future Flag (`future.v7_fetcherPersist`)

Per the same [RFC](https://github.com/remix-run/remix/discussions/7698)
 as above, we've introduced a new `future.v7_fetcherPersist` flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an `idle` state. This makes pending/optimistic UI _much_ easier in scenarios where the originating fetcher needs to unmount.

*   This is sort of a long-standing bug fix as the `useFetchers()` API was always supposed to only reflect **in-flight** fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an `idle` state
*   Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
    *   Fetchers that complete _while still mounted_ will no longer appear in `useFetchers()` after completion - they served no purpose in there since you can access the data via `useFetcher().data`
    *   Fetchers that previously unmounted _while in-flight_ will not be immediately aborted and will instead be cleaned up once they return to an `idle` state
        *   They will remain exposed via `useFetchers` while in-flight so you can still access pending/optimistic data after unmount
        *   If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
        *   However, if a fetcher was re-mounted elsewhere in the tree using the same `key`, then it's result will be processed, even if the originating fetcher was unmounted

### [](#minor-changes-19)
Minor Changes

*   Add fetcher `key` APIs and `navigate=false` options ([#10960](https://github.com/remix-run/react-router/pull/10960)
    )
*   Add `future.v7_fetcherPersist` flag ([#10962](https://github.com/remix-run/react-router/pull/10962)
    )
*   Add support for optional path segments in `matchPath` ([#10768](https://github.com/remix-run/react-router/pull/10768)
    )

### [](#patch-changes-43)
Patch Changes

*   Fix the `future` prop on `BrowserRouter`, `HashRouter` and `MemoryRouter` so that it accepts a `Partial<FutureConfig>` instead of requiring all flags to be included ([#10962](https://github.com/remix-run/react-router/pull/10962)
    )
*   Fix `router.getFetcher`/`router.deleteFetcher` type definitions which incorrectly specified `key` as an optional parameter ([#10960](https://github.com/remix-run/react-router/pull/10960)
    )

**Full Changelog**: [`6.17.0...6.18.0`](https://github.com/remix-run/react-router/compare/react-router@6.17.0...react-router@6.18.0)

[](#v6170)
v6.17.0
------------------

Date: 2023-10-16

### [](#whats-changed-12)
What's Changed

#### [](#view-transitions-)
View Transitions 🚀

We're excited to release experimental support for the [View Transitions API](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition)
 in React Router! You can now trigger navigational DOM updates to be wrapped in `document.startViewTransition` to enable CSS animated transitions on SPA navigations in your application.

The simplest approach to enabling a View Transition in your React Router app is via the new [`<Link unstable_viewTransition>`](https://reactrouter.com/v6/components/link#unstable_viewtransition)
 prop. This will cause the navigation DOM update to be wrapped in `document.startViewTransition` which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

If you need to apply more fine-grained styles for your animations, you can leverage the [`unstable_useViewTransitionState`](https://reactrouter.com/v6/hooks/use-view-transition-state)
 hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

    function ImageLink(to, src, alt) {
      const isTransitioning = unstable_useViewTransitionState(to);
      return (
        <Link to={to} unstable_viewTransition>
          <img
            src={src}
            alt={alt}
            style={{
              viewTransitionName: isTransitioning ? "image-expand" : "",
            }}
          />
        </Link>
      );
    }
    

You can also use the [`<NavLink unstable_viewTransition>`](https://reactrouter.com/v6/components/nav-link#unstable_viewtransition)
 shorthand which will manage the hook usage for you and automatically add a `transitioning` class to the `<a>` during the transition:

    a.transitioning img {
      view-transition-name: "image-expand";
    }
    

    <NavLink to={to} unstable_viewTransition>
      <img src={src} alt={alt} />
    </NavLink>
    

For an example usage of View Transitions, check out [our fork](https://github.com/brophdawg11/react-router-records)
 of the awesome [Astro Records](https://github.com/Charca/astro-records)
 demo.

For more information on using the View Transitions API, please refer to the [Smooth and simple transitions with the View Transitions API](https://developer.chrome.com/docs/web-platform/view-transitions/)
 guide from the Google Chrome team.

### [](#minor-changes-20)
Minor Changes

*   Add support for view transitions ([#10916](https://github.com/remix-run/react-router/pull/10916)
    )

### [](#patch-changes-44)
Patch Changes

*   Log a warning and fail gracefully in `ScrollRestoration` when `sessionStorage` is unavailable ([#10848](https://github.com/remix-run/react-router/pull/10848)
    )
*   Fix `RouterProvider` `future` prop type to be a `Partial<FutureConfig>` so that not all flags must be specified ([#10900](https://github.com/remix-run/react-router/pull/10900)
    )
*   Allow 404 detection to leverage root route error boundary if path contains a URL segment ([#10852](https://github.com/remix-run/react-router/pull/10852)
    )
*   Fix `ErrorResponse` type to avoid leaking internal field ([#10876](https://github.com/remix-run/react-router/pull/10876)
    )

**Full Changelog**: [`6.16.0...6.17.0`](https://github.com/remix-run/react-router/compare/react-router@6.16.0...react-router@6.17.0)

[](#v6160)
v6.16.0
------------------

Date: 2023-09-13

### [](#minor-changes-21)
Minor Changes

*   In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of `any` with `unknown` on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to `any` in React Router and are overridden with `unknown` in Remix. In React Router v7 we plan to move these to `unknown` as a breaking change. ([#10843](https://github.com/remix-run/react-router/pull/10843)
    )
    *   `Location` now accepts a generic for the `location.state` value
    *   `ActionFunctionArgs`/`ActionFunction`/`LoaderFunctionArgs`/`LoaderFunction` now accept a generic for the `context` parameter (only used in SSR usages via `createStaticHandler`)
    *   The return type of `useMatches` (now exported as `UIMatch`) accepts generics for `match.data` and `match.handle` - both of which were already set to `unknown`
*   Move the `@private` class export `ErrorResponse` to an `UNSAFE_ErrorResponseImpl` export since it is an implementation detail and there should be no construction of `ErrorResponse` instances in userland. This frees us up to export a `type ErrorResponse` which correlates to an instance of the class via `InstanceType`. Userland code should only ever be using `ErrorResponse` as a type and should be type-narrowing via `isRouteErrorResponse`. ([#10811](https://github.com/remix-run/react-router/pull/10811)
    )
*   Export `ShouldRevalidateFunctionArgs` interface ([#10797](https://github.com/remix-run/react-router/pull/10797)
    )
*   Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (`_isFetchActionRedirect`, `_hasFetcherDoneAnything`) ([#10715](https://github.com/remix-run/react-router/pull/10715)
    )

### [](#patch-changes-45)
Patch Changes

*   Properly encode rendered URIs in server rendering to avoid hydration errors ([#10769](https://github.com/remix-run/react-router/pull/10769)
    )
*   Add method/url to error message on aborted `query`/`queryRoute` calls ([#10793](https://github.com/remix-run/react-router/pull/10793)
    )
*   Fix a race-condition with loader/action-thrown errors on `route.lazy` routes ([#10778](https://github.com/remix-run/react-router/pull/10778)
    )
*   Fix type for `actionResult` on the arguments object passed to `shouldRevalidate` ([#10779](https://github.com/remix-run/react-router/pull/10779)
    )

**Full Changelog**: [`v6.15.0...v6.16.0`](https://github.com/remix-run/react-router/compare/react-router@6.15.0...react-router@6.16.0)

[](#v6150)
v6.15.0
------------------

Date: 2023-08-10

### [](#minor-changes-22)
Minor Changes

*   Add's a new `redirectDocument()` function which allows users to specify that a redirect from a `loader`/`action` should trigger a document reload (via `window.location`) instead of attempting to navigate to the redirected location via React Router ([#10705](https://github.com/remix-run/react-router/pull/10705)
    )

### [](#patch-changes-46)
Patch Changes

*   Ensure `useRevalidator` is referentially stable across re-renders if revalidations are not actively occurring ([#10707](https://github.com/remix-run/react-router/pull/10707)
    )
*   Ensure hash history always includes a leading slash on hash pathnames ([#10753](https://github.com/remix-run/react-router/pull/10753)
    )
*   Fixes an edge-case affecting web extensions in Firefox that use `URLSearchParams` and the `useSearchParams` hook ([#10620](https://github.com/remix-run/react-router/pull/10620)
    )
*   Reorder effects in `unstable_usePrompt` to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously ([#10687](https://github.com/remix-run/react-router/pull/10687)
    , [#10718](https://github.com/remix-run/react-router/pull/10718)
    )
*   SSR: Do not include hash in `useFormAction()` for unspecified actions since it cannot be determined on the server and causes hydration issues ([#10758](https://github.com/remix-run/react-router/pull/10758)
    )
*   SSR: Fix an issue in `queryRoute` that was not always identifying thrown `Response` instances ([#10717](https://github.com/remix-run/react-router/pull/10717)
    )
*   `react-router-native`: Update `@ungap/url-search-params` dependency from `^0.1.4` to `^0.2.2` ([#10590](https://github.com/remix-run/react-router/pull/10590)
    )

**Full Changelog**: [`v6.14.2...v6.15.0`](https://github.com/remix-run/react-router/compare/react-router@6.14.2...react-router@6.15.0)

[](#v6142)
v6.14.2
------------------

Date: 2023-07-17

### [](#patch-changes-47)
Patch Changes

*   Add missing `<Form state>` prop to populate `history.state` on submission navigations ([#10630](https://github.com/remix-run/react-router/pull/10630)
    )
*   Trigger an error if a `defer` promise resolves/rejects with `undefined` in order to match the behavior of loaders and actions which must return a value or `null` ([#10690](https://github.com/remix-run/react-router/pull/10690)
    )
*   Properly handle fetcher redirects interrupted by normal navigations ([#10674](https://github.com/remix-run/react-router/pull/10674)
    )
*   Initial-load fetchers should not automatically revalidate on GET navigations ([#10688](https://github.com/remix-run/react-router/pull/10688)
    )
*   Properly decode element id when emulating hash scrolling via `<ScrollRestoration>` ([#10682](https://github.com/remix-run/react-router/pull/10682)
    )
*   Typescript: Enhance the return type of `Route.lazy` to prohibit returning an empty object ([#10634](https://github.com/remix-run/react-router/pull/10634)
    )
*   SSR: Support proper hydration of `Error` subclasses such as `ReferenceError`/`TypeError` ([#10633](https://github.com/remix-run/react-router/pull/10633)
    )

**Full Changelog**: [`v6.14.1...v6.14.2`](https://github.com/remix-run/react-router/compare/react-router@6.14.1...react-router@6.14.2)

[](#v6141)
v6.14.1
------------------

Date: 2023-06-30

### [](#patch-changes-48)
Patch Changes

*   Fix loop in `unstable_useBlocker` when used with an unstable blocker function ([#10652](https://github.com/remix-run/react-router/pull/10652)
    )
*   Fix issues with reused blockers on subsequent navigations ([#10656](https://github.com/remix-run/react-router/pull/10656)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.7.1`

**Full Changelog**: [`v6.14.0...v6.14.1`](https://github.com/remix-run/react-router/compare/react-router@6.14.0...react-router@6.14.1)

[](#v6140)
v6.14.0
------------------

Date: 2023-06-23

### [](#whats-changed-13)
What's Changed

#### [](#jsontext-submissions)
JSON/Text Submissions

`6.14.0` adds support for JSON and Text submissions via `useSubmit`/`fetcher.submit` since it's not always convenient to have to serialize into `FormData` if you're working in a client-side SPA. To opt-into these encodings you just need to specify the proper `formEncType`:

**Opt-into `application/json` encoding:**

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit({ key: "value" }, { method: "post", encType: "application/json" });
      // navigation.formEncType => "application/json"
      // navigation.json        => { key: "value" }
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "application/json"
      // await request.json()                => { key: "value" }
    }
    

**Opt-into `text/plain` encoding:**

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit("Text submission", { method: "post", encType: "text/plain" });
      // navigation.formEncType => "text/plain"
      // navigation.text        => "Text submission"
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "text/plain"
      // await request.text()                => "Text submission"
    }
    

**⚠️ Default Behavior Will Change in v7**

Please note that to avoid a breaking change, the default behavior will still encode a simple key/value JSON object into a `FormData` instance:

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit({ key: "value" }, { method: "post" });
      // navigation.formEncType => "application/x-www-form-urlencoded"
      // navigation.formData    => FormData instance
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "application/x-www-form-urlencoded"
      // await request.formData()            => FormData instance
    }
    

This behavior will likely change in v7 so it's best to make any JSON object submissions explicit with `formEncType: "application/x-www-form-urlencoded"` or `formEncType: "application/json"` to ease your eventual v7 migration path.

### [](#minor-changes-23)
Minor Changes

*   Add support for `application/json` and `text/plain` encodings for `useSubmit`/`fetcher.submit`. To reflect these additional types, `useNavigation`/`useFetcher` now also contain `navigation.json`/`navigation.text` and `fetcher.json`/`fetcher.text` which include the json/text submission if applicable. ([#10413](https://github.com/remix-run/react-router/pull/10413)
    )

### [](#patch-changes-49)
Patch Changes

*   When submitting a form from a `submitter` element, prefer the built-in `new FormData(form, submitter)` instead of the previous manual approach in modern browsers (those that support the new `submitter` parameter) ([#9865](https://github.com/remix-run/react-router/pull/9865)
    )
    *   For browsers that don't support it, we continue to just append the submit button's entry to the end, and we also add rudimentary support for `type="image"` buttons
    *   If developers want full spec-compliant support for legacy browsers, they can use the `formdata-submitter-polyfill`
*   Call `window.history.pushState/replaceState` _before_ updating React Router state (instead of after) so that `window.location` matches `useLocation` during synchronous React 17 rendering ([#10448](https://github.com/remix-run/react-router/pull/10448)
    )
    *   ⚠️ Note: generally apps should not be relying on `window.location` and should always reference `useLocation` when possible, as `window.location` will not be in sync 100% of the time (due to `popstate` events, concurrent mode, etc.)
*   Avoid calling `shouldRevalidate` for fetchers that have not yet completed a data load ([#10623](https://github.com/remix-run/react-router/pull/10623)
    )
*   Strip `basename` from the `location` provided to `<ScrollRestoration getKey>` to match the `useLocation` behavior ([#10550](https://github.com/remix-run/react-router/pull/10550)
    )
*   Strip `basename` from locations provided to `unstable_useBlocker` functions to match the `useLocation` behavior ([#10573](https://github.com/remix-run/react-router/pull/10573)
    )
*   Fix `unstable_useBlocker` key issues in `StrictMode` ([#10573](https://github.com/remix-run/react-router/pull/10573)
    )
*   Fix `generatePath` when passed a numeric `0` value parameter ([#10612](https://github.com/remix-run/react-router/pull/10612)
    )
*   Fix `tsc --skipLibCheck:false` issues on React 17 ([#10622](https://github.com/remix-run/react-router/pull/10622)
    )
*   Upgrade `typescript` to 5.1 ([#10581](https://github.com/remix-run/react-router/pull/10581)
    )

**Full Changelog**: [`v6.13.0...v6.14.0`](https://github.com/remix-run/react-router/compare/react-router@6.13.0...react-router@6.14.0)

[](#v6130)
v6.13.0
------------------

Date: 2023-06-14

### [](#whats-changed-14)
What's Changed

`6.13.0` is really a patch release in spirit but comes with a SemVer minor bump since we added a new future flag.

#### [](#futurev7_starttransition)
`future.v7_startTransition`

The **tl;dr;** is that `6.13.0` is the same as [`6.12.0`](https://github.com/remix-run/react-router/releases/tag/react-router%406.12.0)
 bue we've moved the usage of `React.startTransition` behind an opt-in `future.v7_startTransition` [future flag](https://reactrouter.com/v6/guides/api-development-strategy)
 because we found that there are applications in the wild that are currently using `Suspense` in ways that are incompatible with `React.startTransition`.

Therefore, in `6.13.0` the default behavior will no longer leverage `React.startTransition`:

    <BrowserRouter>
      <Routes>{/*...*/}</Routes>
    </BrowserRouter>
    
    <RouterProvider router={router} />
    

If you wish to enable `React.startTransition`, pass the future flag to your router component:

    <BrowserRouter future={{ v7_startTransition: true }}>
      <Routes>{/*...*/}</Routes>
    </BrowserRouter>
    
    <RouterProvider router={router} future={{ v7_startTransition: true }}/>
    

We recommend folks adopt this flag sooner rather than later to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of `React.startTransition` until v7. Issues usually boil down to creating net-new promises during the render cycle, so if you run into issues when opting into `React.startTransition`, you should either lift your promise creation out of the render cycle or put it behind a `useMemo`.

### [](#minor-changes-24)
Minor Changes

*   Move `React.startTransition` usage behinds a future flag ([#10596](https://github.com/remix-run/react-router/pull/10596)
    )

### [](#patch-changes-50)
Patch Changes

*   Work around webpack/terser `React.startTransition` minification bug in production mode ([#10588](https://github.com/remix-run/react-router/pull/10588)
    )

**Full Changelog**: [`v6.12.1...v6.13.0`](https://github.com/remix-run/react-router/compare/react-router@6.12.1...react-router@6.13.0)

[](#v6121)
v6.12.1
------------------

Date: 2023-06-08

> \[!WARNING\] Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569)
>  and [#10579](https://github.com/remix-run/react-router/issues/10579)
>  for more details.

### [](#patch-changes-51)
Patch Changes

*   Adjust feature detection of `React.startTransition` to fix webpack + react 17 compilation error ([#10569](https://github.com/remix-run/react-router/pull/10569)
    )

**Full Changelog**: [`v6.12.0...v6.12.1`](https://github.com/remix-run/react-router/compare/react-router@6.12.0...react-router@6.12.1)

[](#v6120)
v6.12.0
------------------

Date: 2023-06-06

> \[!WARNING\] Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569)
>  and [#10579](https://github.com/remix-run/react-router/issues/10579)
>  for more details.

### [](#whats-changed-15)
What's Changed

#### [](#reactstarttransition-support)
`React.startTransition` support

With `6.12.0` we've added better support for suspending components by wrapping the internal router state updates in [`React.startTransition`](https://react.dev/reference/react/startTransition)
. This means that, for example, if one of your components in a destination route suspends and you have not provided a [`Suspense`](https://react.dev/reference/react/Suspense)
 boundary to show a fallback, React will delay the rendering of the new UI and show the old UI until that asynchronous operation resolves. This could be useful for waiting for things such as waiting for images or CSS files to load (and technically, yes, you could use it for data loading but we'd still recommend using loaders for that 😀). For a quick overview of this usage, check out [Ryan's demo on Twitter](https://twitter.com/remix_run/status/1658976420767604736)
.

### [](#minor-changes-25)
Minor Changes

*   Wrap internal router state updates with `React.startTransition` ([#10438](https://github.com/remix-run/react-router/pull/10438)
    )

### [](#patch-changes-52)
Patch Changes

*   Allow fetcher revalidations to complete if submitting fetcher is deleted ([#10535](https://github.com/remix-run/react-router/pull/10535)
    )
*   Re-throw `DOMException` (`DataCloneError`) when attempting to perform a `PUSH` navigation with non-serializable state. ([#10427](https://github.com/remix-run/react-router/pull/10427)
    )
*   Ensure revalidations happen when hash is present ([#10516](https://github.com/remix-run/react-router/pull/10516)
    )
*   Upgrade `jest` and `jsdom` ([#10453](https://github.com/remix-run/react-router/pull/10453)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.6.3` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#163)
        )

**Full Changelog**: [`v6.11.2...v6.12.0`](https://github.com/remix-run/react-router/compare/react-router@6.11.2...react-router@6.12.0)

[](#v6112)
v6.11.2
------------------

Date: 2023-05-17

### [](#patch-changes-53)
Patch Changes

*   Fix `basename` duplication in descendant `<Routes>` inside a `<RouterProvider>` ([#10492](https://github.com/remix-run/react-router/pull/10492)
    )
*   Fix bug where initial data load would not kick off when hash is present ([#10493](https://github.com/remix-run/react-router/pull/10493)
    )
*   Export `SetURLSearchParams` type ([#10444](https://github.com/remix-run/react-router/pull/10444)
    )
*   Fix Remix HMR-driven error boundaries by properly reconstructing new routes and `manifest` in `_internalSetRoutes` ([#10437](https://github.com/remix-run/react-router/pull/10437)
    )

**Full Changelog**: [`v6.11.1...v6.11.2`](https://github.com/remix-run/react-router/compare/react-router@6.11.1...react-router@6.11.2)

[](#v6111)
v6.11.1
------------------

Date: 2023-05-03

### [](#patch-changes-54)
Patch Changes

*   Fix usage of `Component` API within descendant `<Routes>` ([#10434](https://github.com/remix-run/react-router/pull/10434)
    )
*   Fix bug when calling `useNavigate` from `<Routes>` inside a `<RouterProvider>` ([#10432](https://github.com/remix-run/react-router/pull/10432)
    )
*   Fix usage of `<Navigate>` in strict mode when using a data router ([#10435](https://github.com/remix-run/react-router/pull/10435)
    )
*   Fix `basename` handling when navigating without a path ([#10433](https://github.com/remix-run/react-router/pull/10433)
    )
*   "Same hash" navigations no longer re-run loaders to match browser behavior (i.e. `/path#hash -> /path#hash`) ([#10408](https://github.com/remix-run/react-router/pull/10408)
    )

**Full Changelog**: [`v6.11.0...v6.11.1`](https://github.com/remix-run/react-router/compare/react-router@6.11.0...react-router@6.11.1)

[](#v6110)
v6.11.0
------------------

Date: 2023-04-28

### [](#minor-changes-26)
Minor Changes

*   Enable `basename` support in `useFetcher` ([#10336](https://github.com/remix-run/react-router/pull/10336)
    )
    *   If you were previously working around this issue by manually prepending the `basename` then you will need to remove the manually prepended `basename` from your `fetcher` calls (`fetcher.load('/basename/route') -> fetcher.load('/route')`)
*   Updated dependencies:
    *   `@remix-run/router@1.6.0` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#160)
        )

### [](#patch-changes-55)
Patch Changes

*   When using a `RouterProvider`, `useNavigate`/`useSubmit`/`fetcher.submit` are now stable across location changes, since we can handle relative routing via the `@remix-run/router` instance and get rid of our dependence on `useLocation()` ([#10336](https://github.com/remix-run/react-router/pull/10336)
    )
    *   When using `BrowserRouter`, these hooks remain unstable across location changes because they still rely on `useLocation()`
*   Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on `action` submissions or `router.revalidate` calls ([#10344](https://github.com/remix-run/react-router/pull/10344)
    )
*   Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287)
    )
*   Fail gracefully on `<Link to="//">` and other invalid URL values ([#10367](https://github.com/remix-run/react-router/pull/10367)
    )
*   Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81)
     where router state updates got propagated _before_ other normal `useState` updates, which could lead to foot guns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377)
    , [#10409](https://github.com/remix-run/react-router/pull/10409)
    )
*   Log loader/action errors caught by the default error boundary to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286)
    )
*   Fix bug preventing rendering of descendant `<Routes>` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374)
    )
*   Fix detection of `useNavigate` in the render cycle by setting the `activeRef` in a layout effect, allowing the `navigate` function to be passed to child components and called in a `useEffect` there ([#10394](https://github.com/remix-run/react-router/pull/10394)
    )
*   Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369)
    )
*   Enhance `LoaderFunction`/`ActionFunction` return type to prevent `undefined` from being a valid return value ([#10267](https://github.com/remix-run/react-router/pull/10267)
    )
*   Ensure proper 404 error on `fetcher.load` call to a route without a `loader` ([#10345](https://github.com/remix-run/react-router/pull/10345)
    )
*   Decouple `AbortController` usage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation ([#10271](https://github.com/remix-run/react-router/pull/10271)
    )

**Full Changelog**: [`v6.10.0...v6.11.0`](https://github.com/remix-run/react-router/compare/react-router@6.10.0...react-router@6.11.0)

[](#v6100)
v6.10.0
------------------

Date: 2023-03-29

### [](#whats-changed-16)
What's Changed

We recently published a post over on the Remix Blog titled ["Future Proofing Your Remix App"](https://remix.run/blog/future-flags)
 that goes through our strategy to ensure smooth upgrades for your Remix and React Router apps going forward. React Router `6.10.0` adds support for these flags (for data routers) which you can specify when you create your router:

    const router = createBrowserRouter(routes, {
      future: {
        // specify future flags here
      },
    });
    

You can also check out the docs [here](https://reactrouter.com/en/dev/guides/api-development-strategy)
 and [here](https://reactrouter.com/en/dev/routers/create-browser-router#future)
.

### [](#minor-changes-27)
Minor Changes

#### [](#futurev7_normalizeformmethod)
`future.v7_normalizeFormMethod`

The first future flag being introduced is `future.v7_normalizeFormMethod` which will normalize the exposed `useNavigation()/useFetcher()` `formMethod` fields as uppercase HTTP methods to align with the `fetch()` (and some Remix) behavior. ([#10207](https://github.com/remix-run/react-router/pull/10207)
)

*   When `future.v7_normalizeFormMethod` is unspecified or set to `false` (default v6 behavior),
    *   `useNavigation().formMethod` is lowercase
    *   `useFetcher().formMethod` is lowercase
*   When `future.v7_normalizeFormMethod === true`:
    *   `useNavigation().formMethod` is UPPERCASE
    *   `useFetcher().formMethod` is UPPERCASE

### [](#patch-changes-56)
Patch Changes

*   Fix `createStaticHandler` to also check for `ErrorBoundary` on routes in addition to `errorElement` ([#10190](https://github.com/remix-run/react-router/pull/10190)
    )
*   Fix route ID generation when using Fragments in `createRoutesFromElements` ([#10193](https://github.com/remix-run/react-router/pull/10193)
    )
*   Provide fetcher submission to `shouldRevalidate` if the fetcher action redirects ([#10208](https://github.com/remix-run/react-router/pull/10208)
    )
*   Properly handle `lazy()` errors during router initialization ([#10201](https://github.com/remix-run/react-router/pull/10201)
    )
*   Remove `instanceof` check for `DeferredData` to be resilient to ESM/CJS boundaries in SSR bundling scenarios ([#10247](https://github.com/remix-run/react-router/pull/10247)
    )
*   Update to latest `@remix-run/web-fetch@4.3.3` ([#10216](https://github.com/remix-run/react-router/pull/10216)
    )

**Full Changelog**: [`v6.9.0...v6.10.0`](https://github.com/remix-run/react-router/compare/react-router@6.9.0...react-router@6.10.0)

[](#v690)
v6.9.0
----------------

Date: 2023-03-10

### [](#whats-changed-17)
What's Changed

#### [](#componenterrorboundary-route-properties)
`Component`/`ErrorBoundary` route properties

React Router now supports an alternative way to define your route `element` and `errorElement` fields as React Components instead of React Elements. You can instead pass a React Component to the new `Component` and `ErrorBoundary` fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do `Component`/`ErrorBoundary` will "win"

**Example JSON Syntax**

    // Both of these work the same:
    const elementRoutes = [{\
      path: '/',\
      element: <Home />,\
      errorElement: <HomeError />,\
    }]
    
    const componentRoutes = [{\
      path: '/',\
      Component: Home,\
      ErrorBoundary: HomeError,\
    }]
    
    function Home() { ... }
    function HomeError() { ... }
    

**Example JSX Syntax**

    // Both of these work the same:
    const elementRoutes = createRoutesFromElements(
      <Route path='/' element={<Home />} errorElement={<HomeError /> } />
    );
    
    const componentRoutes = createRoutesFromElements(
      <Route path='/' Component={Home} ErrorBoundary={HomeError} />
    );
    
    function Home() { ... }
    function HomeError() { ... }
    

#### [](#introducing-lazy-route-modules)
Introducing Lazy Route Modules

In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new `lazy()` route property. This is an async function that resolves the non-route-matching portions of your route definition (`loader`, `action`, `element`/`Component`, `errorElement`/`ErrorBoundary`, `shouldRevalidate`, `handle`).

Lazy routes are resolved on initial load and during the `loading` or `submitting` phase of a navigation or fetcher call. You cannot lazily define route-matching properties (`path`, `index`, `children`) since we only execute your lazy route functions after we've matched known routes.

Your `lazy` functions will typically return the result of a dynamic import.

    // In this example, we assume most folks land on the homepage so we include that
    // in our critical-path bundle, but then we lazily load modules for /a and /b so
    // they don't load until the user navigates to those routes
    let routes = createRoutesFromElements(
      <Route path="/" element={<Layout />}>
        <Route index element={<Home />} />
        <Route path="a" lazy={() => import("./a")} />
        <Route path="b" lazy={() => import("./b")} />
      </Route>
    );
    

Then in your lazy route modules, export the properties you want defined for the route:

    export async function loader({ request }) {
      let data = await fetchData(request);
      return json(data);
    }
    
    // Export a `Component` directly instead of needing to create a React Element from it
    export function Component() {
      let data = useLoaderData();
    
      return (
        <>
          <h1>You made it!</h1>
          <p>{data}</p>
        </>
      );
    }
    
    // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
    export function ErrorBoundary() {
      let error = useRouteError();
      return isRouteErrorResponse(error) ? (
        <h1>
          {error.status} {error.statusText}
        </h1>
      ) : (
        <h1>{error.message || error}</h1>
      );
    }
    

An example of this in action can be found in the [`examples/lazy-loading-router-provider`](https://github.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider)
 directory of the repository. For more info, check out the [`lazy` docs](https://reactrouter.com/v6/route/lazy)
.

🙌 Huge thanks to @rossipedia for the [Initial Proposal](https://github.com/remix-run/react-router/discussions/9826)
 and [POC Implementation](https://github.com/remix-run/react-router/pull/9830)
.

### [](#minor-changes-28)
Minor Changes

*   Add support for `route.Component`/`route.ErrorBoundary` properties ([#10045](https://github.com/remix-run/react-router/pull/10045)
    )
*   Add support for `route.lazy` ([#10045](https://github.com/remix-run/react-router/pull/10045)
    )

### [](#patch-changes-57)
Patch Changes

*   Improve memoization for context providers to avoid unnecessary re-renders ([#9983](https://github.com/remix-run/react-router/pull/9983)
    )
*   Fix `generatePath` incorrectly applying parameters in some cases ([#10078](https://github.com/remix-run/react-router/pull/10078)
    )
*   `[react-router-dom-v5-compat]` Add missed data router API re-exports ([#10171](https://github.com/remix-run/react-router/pull/10171)
    )

**Full Changelog**: [`v6.8.2...v6.9.0`](https://github.com/remix-run/react-router/compare/react-router@6.8.2...react-router@6.9.0)

[](#v682)
v6.8.2
----------------

Date: 2023-02-27

### [](#patch-changes-58)
Patch Changes

*   Treat same-origin absolute URLs in `<Link to>` as external if they are outside of the router `basename` ([#10135](https://github.com/remix-run/react-router/pull/10135)
    )
*   Correctly perform a hard redirect for same-origin absolute URLs outside of the router `basename` ([#10076](https://github.com/remix-run/react-router/pull/10076)
    )
*   Fix SSR of absolute `<Link to>` urls ([#10112](https://github.com/remix-run/react-router/pull/10112)
    )
*   Properly escape HTML characters in `StaticRouterProvider` serialized hydration data ([#10068](https://github.com/remix-run/react-router/pull/10068)
    )
*   Fix `useBlocker` to return `IDLE_BLOCKER` during SSR ([#10046](https://github.com/remix-run/react-router/pull/10046)
    )
*   Ensure status code and headers are maintained for `defer` loader responses in `createStaticHandler`'s `query()` method ([#10077](https://github.com/remix-run/react-router/pull/10077)
    )
*   Change `invariant` to an `UNSAFE_invariant` export since it's only intended for internal use ([#10066](https://github.com/remix-run/react-router/pull/10066)
    )

**Full Changelog**: [`v6.8.1...v6.8.2`](https://github.com/remix-run/react-router/compare/react-router@6.8.1...react-router@6.8.2)

[](#v681)
v6.8.1
----------------

Date: 2023-02-06

### [](#patch-changes-59)
Patch Changes

*   Remove inaccurate console warning for POP navigations and update active blocker logic ([#10030](https://github.com/remix-run/react-router/pull/10030)
    )
*   Only check for differing origin on absolute URL redirects ([#10033](https://github.com/remix-run/react-router/pull/10033)
    )
*   Improved absolute url detection in `Link` component (now also supports `mailto:` urls) ([#9994](https://github.com/remix-run/react-router/pull/9994)
    )
*   Fix partial object (search or hash only) pathnames losing current path value ([#10029](https://github.com/remix-run/react-router/pull/10029)
    )

**Full Changelog**: [`v6.8.0...v6.8.1`](https://github.com/remix-run/react-router/compare/react-router@6.8.0...react-router@6.8.1)

[](#v680)
v6.8.0
----------------

Date: 2023-01-26

### [](#minor-changes-29)
Minor Changes

Support absolute URLs in `<Link to>`. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. ([#9900](https://github.com/remix-run/react-router/pull/9900)
)

    <Link to="https://neworigin.com/some/path">    {/* Document request */}
    <Link to="//neworigin.com/some/path">          {/* Document request */}
    <Link to="https://www.currentorigin.com/path"> {/* Client-side navigation */}
    

### [](#patch-changes-60)
Patch Changes

*   Fixes 2 separate issues for revalidating fetcher `shouldRevalidate` calls ([#9948](https://github.com/remix-run/react-router/pull/9948)
    )
    *   The `shouldRevalidate` function was only being called for _explicit_ revalidation scenarios (after a mutation, manual `useRevalidator` call, or an `X-Remix-Revalidate` header used for cookie setting in Remix). It was not properly being called on _implicit_ revalidation scenarios that also apply to navigation `loader` revalidation, such as a change in search params or clicking a link for the page we're already on. It's now correctly called in those additional scenarios.
    *   The parameters being passed were incorrect and inconsistent with one another since the `current*`/`next*` parameters reflected the static `fetcher.load` URL (and thus were identical). Instead, they should have reflected the navigation that triggered the revalidation (as the `form*` parameters did). These parameters now correctly reflect the triggering navigation.
*   Fix bug with search params removal via `useSearchParams` ([#9969](https://github.com/remix-run/react-router/pull/9969)
    )
*   Respect `preventScrollReset` on `<fetcher.Form>` ([#9963](https://github.com/remix-run/react-router/pull/9963)
    )
*   Fix navigation for hash routers on manual URL changes ([#9980](https://github.com/remix-run/react-router/pull/9980)
    )
*   Use `pagehide` instead of `beforeunload` for `<ScrollRestoration>`. This has better cross-browser support, specifically on Mobile Safari. ([#9945](https://github.com/remix-run/react-router/pull/9945)
    )
*   Do not short circuit on hash change only mutation submissions ([#9944](https://github.com/remix-run/react-router/pull/9944)
    )
*   Remove `instanceof` check from `isRouteErrorResponse` to avoid bundling issues on the server ([#9930](https://github.com/remix-run/react-router/pull/9930)
    )
*   Detect when a `defer` call only contains critical data and remove the `AbortController` ([#9965](https://github.com/remix-run/react-router/pull/9965)
    )
*   Send the name as the value when url-encoding `File` `FormData` entries ([#9867](https://github.com/remix-run/react-router/pull/9867)
    )
*   `react-router-dom-v5-compat` - Fix SSR `useLayoutEffect` `console.error` when using `CompatRouter` ([#9820](https://github.com/remix-run/react-router/pull/9820)
    )

**Full Changelog**: [`v6.7.0...v6.8.0`](https://github.com/remix-run/react-router/compare/react-router@6.7.0...react-router@6.8.0)

[](#v670)
v6.7.0
----------------

Date: 2023-01-18

### [](#minor-changes-30)
Minor Changes

*   Add `unstable_useBlocker`/`unstable_usePrompt` hooks for blocking navigations within the app's location origin ([#9709](https://github.com/remix-run/react-router/pull/9709)
    , [#9932](https://github.com/remix-run/react-router/pull/9932)
    )
*   Add `preventScrollReset` prop to `<Form>` ([#9886](https://github.com/remix-run/react-router/pull/9886)
    )

### [](#patch-changes-61)
Patch Changes

*   Added pass-through event listener options argument to `useBeforeUnload` ([#9709](https://github.com/remix-run/react-router/pull/9709)
    )
*   Fix `generatePath` when optional params are present ([#9764](https://github.com/remix-run/react-router/pull/9764)
    )
*   Update `<Await>` to accept `ReactNode` as children function return result ([#9896](https://github.com/remix-run/react-router/pull/9896)
    )
*   Improved absolute redirect url detection in actions/loaders ([#9829](https://github.com/remix-run/react-router/pull/9829)
    )
*   Fix URL creation with memory histories ([#9814](https://github.com/remix-run/react-router/pull/9814)
    )
*   Fix scroll reset if a submission redirects ([#9886](https://github.com/remix-run/react-router/pull/9886)
    )
*   Fix 404 bug with same-origin absolute redirects ([#9913](https://github.com/remix-run/react-router/pull/9913)
    )
*   Streamline `jsdom` bug workaround in tests ([#9824](https://github.com/remix-run/react-router/pull/9824)
    )

**Full Changelog**: [`v6.6.2...v6.7.0`](https://github.com/remix-run/react-router/compare/react-router@6.6.2...react-router@6.7.0)

[](#v662)
v6.6.2
----------------

Date: 2023-01-09

### [](#patch-changes-62)
Patch Changes

*   Ensure `useId` consistency during SSR ([#9805](https://github.com/remix-run/react-router/pull/9805)
    )

**Full Changelog**: [`v6.6.1...v6.6.2`](https://github.com/remix-run/react-router/compare/react-router@6.6.1...react-router@6.6.2)

[](#v661)
v6.6.1
----------------

Date: 2022-12-23

### [](#patch-changes-63)
Patch Changes

*   Include submission info in `shouldRevalidate` on action redirects ([#9777](https://github.com/remix-run/react-router/pull/9777)
    , [#9782](https://github.com/remix-run/react-router/pull/9782)
    )
*   Reset `actionData` on action redirect to current location ([#9772](https://github.com/remix-run/react-router/pull/9772)
    )

**Full Changelog**: [`v6.6.0...v6.6.1`](https://github.com/remix-run/react-router/compare/react-router@6.6.0...react-router@6.6.1)

[](#v660)
v6.6.0
----------------

Date: 2022-12-21

### [](#whats-changed-18)
What's Changed

This minor release is primarily to stabilize our SSR APIs for Data Routers now that we've wired up the new `RouterProvider` in Remix as part of the [React Router-ing Remix](https://remix.run/blog/react-routering-remix)
 work.

### [](#minor-changes-31)
Minor Changes

*   Remove `unstable_` prefix from `createStaticHandler`/`createStaticRouter`/`StaticRouterProvider` ([#9738](https://github.com/remix-run/react-router/pull/9738)
    )
*   Add `useBeforeUnload()` hook ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )

### [](#patch-changes-64)
Patch Changes

*   Support uppercase `<Form method>` and `useSubmit` method values ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix `<button formmethod>` form submission overriddes ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix explicit `replace` on submissions and `PUSH` on submission to new paths ([#9734](https://github.com/remix-run/react-router/pull/9734)
    )
*   Prevent `useLoaderData` usage in `errorElement` ([#9735](https://github.com/remix-run/react-router/pull/9735)
    )
*   Proper hydration of `Error` objects from `StaticRouterProvider` ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Skip initial scroll restoration for SSR apps with `hydrationData` ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix a few bugs where loader/action data wasn't properly cleared on errors ([#9735](https://github.com/remix-run/react-router/pull/9735)
    )

**Full Changelog**: [`v6.5.0...v6.6.0`](https://github.com/remix-run/react-router/compare/react-router@6.5.0...react-router@6.6.0)

[](#v650)
v6.5.0
----------------

Date: 2022-12-16

### [](#whats-changed-19)
What's Changed

This release introduces support for [Optional Route Segments](https://github.com/remix-run/react-router/issues/9546)
. Now, adding a `?` to the end of any path segment will make that entire segment optional. This works for both static segments and dynamic parameters.

**Optional Params Examples**

*   `<Route path=":lang?/about>` will match:
    *   `/:lang/about`
    *   `/about`
*   `<Route path="/multistep/:widget1?/widget2?/widget3?">` will match:
    *   `/multistep`
    *   `/multistep/:widget1`
    *   `/multistep/:widget1/:widget2`
    *   `/multistep/:widget1/:widget2/:widget3`

**Optional Static Segment Example**

*   `<Route path="/home?">` will match:
    *   `/`
    *   `/home`
*   `<Route path="/fr?/about">` will match:
    *   `/about`
    *   `/fr/about`

### [](#minor-changes-32)
Minor Changes

*   Allows optional routes and optional static segments ([#9650](https://github.com/remix-run/react-router/pull/9650)
    )

### [](#patch-changes-65)
Patch Changes

*   Stop incorrectly matching on partial named parameters, i.e. `<Route path="prefix-:param">`, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the `useParams` call site: ([#9506](https://github.com/remix-run/react-router/pull/9506)
    )

    // Old behavior at URL /prefix-123
    <Route path="prefix-:id" element={<Comp /> }>
    
    function Comp() {
      let params = useParams(); // { id: '123' }
      let id = params.id; // "123"
      ...
    }
    
    // New behavior at URL /prefix-123
    <Route path=":id" element={<Comp /> }>
    
    function Comp() {
      let params = useParams(); // { id: 'prefix-123' }
      let id = params.id.replace(/^prefix-/, ''); // "123"
      ...
    }
    

*   Persist `headers` on `loader` `request`'s after SSR document `action` request ([#9721](https://github.com/remix-run/react-router/pull/9721)
    )
*   Fix requests sent to revalidating loaders so they reflect a GET request ([#9660](https://github.com/remix-run/react-router/pull/9660)
    )
*   Fix issue with deeply nested optional segments ([#9727](https://github.com/remix-run/react-router/pull/9727)
    )
*   GET forms now expose a submission on the loading navigation ([#9695](https://github.com/remix-run/react-router/pull/9695)
    )
*   Fix error boundary tracking for multiple errors bubbling to the same boundary ([#9702](https://github.com/remix-run/react-router/pull/9702)
    )

**Full Changelog**: [`v6.4.5...v6.5.0`](https://github.com/remix-run/react-router/compare/react-router@6.4.5...react-router@6.5.0)

[](#v645)
v6.4.5
----------------

Date: 2022-12-07

### [](#patch-changes-66)
Patch Changes

*   Fix requests sent to revalidating loaders so they reflect a `GET` request ([#9680](https://github.com/remix-run/react-router/pull/9680)
    )
*   Remove `instanceof Response` checks in favor of `isResponse` ([#9690](https://github.com/remix-run/react-router/pull/9690)
    )
*   Fix `URL` creation in Cloudflare Pages or other non-browser-environments ([#9682](https://github.com/remix-run/react-router/pull/9682)
    , [#9689](https://github.com/remix-run/react-router/pull/9689)
    )
*   Add `requestContext` support to static handler `query`/`queryRoute` ([#9696](https://github.com/remix-run/react-router/pull/9696)
    )
    *   Note that the unstable API of `queryRoute(path, routeId)` has been changed to `queryRoute(path, { routeId, requestContext })`

**Full Changelog**: [`v6.4.4...v6.4.5`](https://github.com/remix-run/react-router/compare/react-router@6.4.4...react-router@6.4.5)

[](#v644)
v6.4.4
----------------

Date: 2022-11-30

### [](#patch-changes-67)
Patch Changes

*   Throw an error if an `action`/`loader` function returns `undefined` as revalidations need to know whether the loader has previously been executed. `undefined` also causes issues during SSR stringification for hydration. You should always ensure your `loader`/`action` returns a value, and you may return `null` if you don't wish to return anything. ([#9511](https://github.com/remix-run/react-router/pull/9511)
    )
*   Properly handle redirects to external domains ([#9590](https://github.com/remix-run/react-router/pull/9590)
    , [#9654](https://github.com/remix-run/react-router/pull/9654)
    )
*   Preserve the HTTP method on 307/308 redirects ([#9597](https://github.com/remix-run/react-router/pull/9597)
    )
*   Support `basename` in static data routers ([#9591](https://github.com/remix-run/react-router/pull/9591)
    )
*   Enhanced `ErrorResponse` bodies to contain more descriptive text in internal 403/404/405 scenarios
*   Fix issues with encoded characters in `NavLink` and descendant `<Routes>` ([#9589](https://github.com/remix-run/react-router/pull/9589)
    , [#9647](https://github.com/remix-run/react-router/pull/9647)
    )
*   Properly serialize/deserialize `ErrorResponse` instances when using built-in hydration ([#9593](https://github.com/remix-run/react-router/pull/9593)
    )
*   Support `basename` in static data routers ([#9591](https://github.com/remix-run/react-router/pull/9591)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.0.4`
    *   `react-router@6.4.4`

**Full Changelog**: [`v6.4.3...v6.4.4`](https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4)

[](#v643)
v6.4.3
----------------

Date: 2022-11-01

### [](#patch-changes-68)
Patch Changes

*   Generate correct `<a href>` values when using `createHashRouter` ([#9409](https://github.com/remix-run/react-router/pull/9409)
    )
*   Better handle encoding/matching with special characters in URLs and route paths ([#9477](https://github.com/remix-run/react-router/pull/9477)
    , [#9496](https://github.com/remix-run/react-router/pull/9496)
    )
*   Generate correct `formAction` pathnames when an `index` route also has a `path` ([#9486](https://github.com/remix-run/react-router/pull/9486)
    )
*   Respect `relative=path` prop on `NavLink` ([#9453](https://github.com/remix-run/react-router/pull/9453)
    )
*   Fix `NavLink` behavior for root urls ([#9497](https://github.com/remix-run/react-router/pull/9497)
    )
*   `useRoutes` should be able to return `null` when passing `locationArg` ([#9485](https://github.com/remix-run/react-router/pull/9485)
    )
*   Fix `initialEntries` type in `createMemoryRouter` ([#9498](https://github.com/remix-run/react-router/pull/9498)
    )
*   Support `basename` and relative routing in `loader`/`action` redirects ([#9447](https://github.com/remix-run/react-router/pull/9447)
    )
*   Ignore pathless layout routes when looking for proper submission `action` function ([#9455](https://github.com/remix-run/react-router/pull/9455)
    )
*   Add UMD build for `@remix-run/router` ([#9446](https://github.com/remix-run/react-router/pull/9446)
    )
*   Fix `createURL` in local file execution in Firefox ([#9464](https://github.com/remix-run/react-router/pull/9464)
    )

**Full Changelog**: [`v6.4.2...v6.4.3`](https://github.com/remix-run/react-router/compare/react-router@6.4.2...react-router@6.4.3)

[](#v642)
v6.4.2
----------------

Date: 2022-10-06

### [](#patch-changes-69)
Patch Changes

*   Respect `basename` in `useFormAction` ([#9352](https://github.com/remix-run/react-router/pull/9352)
    )
*   Fix `IndexRouteObject` and `NonIndexRouteObject` types to make `hasErrorElement` optional ([#9394](https://github.com/remix-run/react-router/pull/9394)
    )
*   Enhance console error messages for invalid usage of data router hooks ([#9311](https://github.com/remix-run/react-router/pull/9311)
    )
*   If an index route has children, it will result in a runtime error. We have strengthened our `RouteObject`/`RouteProps` types to surface the error in TypeScript. ([#9366](https://github.com/remix-run/react-router/pull/9366)
    )

**Full Changelog**: [`v6.4.1...v6.4.2`](https://github.com/remix-run/react-router/compare/react-router@6.4.1...react-router@6.4.2)

[](#v641)
v6.4.1
----------------

Date: 2022-09-22

### [](#patch-changes-70)
Patch Changes

*   Preserve state from `initialEntries` ([#9288](https://github.com/remix-run/react-router/pull/9288)
    )
*   Preserve `?index` for fetcher get submissions to index routes ([#9312](https://github.com/remix-run/react-router/pull/9312)
    )

**Full Changelog**: [`v6.4.0...v6.4.1`](https://github.com/remix-run/react-router/compare/react-router@6.4.0...react-router@6.4.1)

[](#v640)
v6.4.0
----------------

Date: 2022-09-13

### [](#whats-changed-20)
What's Changed

#### [](#remix-data-apis)
Remix Data APIs

Whoa this is a big one! `6.4.0` brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the [docs](https://reactrouter.com/)
, especially the [feature overview](https://reactrouter.com/en/6.4.0/start/overview)
 and the [tutorial](https://reactrouter.com/en/6.4.0/start/tutorial)
.

**New `react-router` APIs**

*   Create your router with `createMemoryRouter`
*   Render your router with `<RouterProvider>`
*   Load data with a Route `loader` and mutate with a Route `action`
*   Handle errors with Route `errorElement`
*   Defer non-critical data with `defer` and `Await`

**New `react-router-dom` APIs**

*   Create your router with `createBrowserRouter`/`createHashRouter`
*   Submit data with the new `<Form>` component
*   Perform in-page data loads and mutations with `useFetcher()`
*   Defer non-critical data with `defer` and `Await`
*   Manage scroll position with `<ScrollRestoration>`
*   Perform path-relative navigations with `<Link relative="path">` ([#9160](https://github.com/remix-run/react-router/pull/9160)
    )

### [](#patch-changes-71)
Patch Changes

*   Path resolution is now trailing slash agnostic ([#8861](https://github.com/remix-run/react-router/pull/8861)
    )
*   `useLocation` returns the scoped location inside a `<Routes location>` component ([#9094](https://github.com/remix-run/react-router/pull/9094)
    )
*   Respect the `<Link replace>` prop if it is defined ([#8779](https://github.com/remix-run/react-router/pull/8779)
    )

**Full Changelog**: [`v6.3.0...v6.4.0`](https://github.com/remix-run/react-router/compare/v6.3.0...react-router%406.4.0)

[](#v630)
v6.3.0
----------------

Date: 2022-03-31

### [](#minor-changes-33)
Minor Changes

*   Added the v5 to v6 backwards compatibility package 💜 ([#8752](https://github.com/remix-run/react-router/pull/8752)
    ). The official guide can be found [in this discussion](https://github.com/remix-run/react-router/discussions/8753)
    

**Full Changelog**: [`v6.2.2...v6.3.0`](https://github.com/remix-run/react-router/compare/v6.2.2...v6.3.0)

[](#v622)
v6.2.2
----------------

Date: 2022-02-28

### [](#patch-changes-72)
Patch Changes

*   Fixed nested splat routes that begin with special URL-safe characters ([#8563](https://github.com/remix-run/react-router/pull/8563)
    )
*   Fixed a bug where index routes were missing route context in some cases ([#8497](https://github.com/remix-run/react-router/pull/8497)
    )

**Full Changelog**: [`v6.2.1...v6.2.2`](https://github.com/remix-run/react-router/compare/v6.2.1...v6.2.2)

[](#v621)
v6.2.1
----------------

Date: 2021-12-17

### [](#patch-changes-73)
Patch Changes

*   This release updates the internal `history` dependency to `5.2.0`.

**Full Changelog**: [`v6.2.0...v6.2.1`](https://github.com/remix-run/react-router/compare/v6.2.0...v6.2.1)

[](#v620)
v6.2.0
----------------

Date: 2021-12-17

### [](#minor-changes-34)
Minor Changes

*   We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts ([See the commit](https://github.com/remix-run/react-router/commit/29c7fc8b5f853b0b06ecd0f5682a9bbe6eca0715)
    ).

### [](#patch-changes-74)
Patch Changes

*   Fixed the `RouteProps` `element` type, which should be a `ReactNode` ([#8473](https://github.com/remix-run/react-router/pull/8473)
    )
*   Fixed a bug with `useOutlet` for top-level routes ([#8483](https://github.com/remix-run/react-router/pull/8483)
    )

**Full Changelog**: [`v6.1.1...v6.2.0`](https://github.com/remix-run/react-router/compare/v6.1.1...v6.2.0)

[](#v611)
v6.1.1
----------------

Date: 2021-12-11

### [](#patch-changes-75)
Patch Changes

*   In v6.1.0 we inadvertently shipped a new, undocumented API that will likely introduce bugs ([#7586](https://github.com/remix-run/react-router/pull/7586)
    ). We have flagged `HistoryRouter` as `unstable_HistoryRouter`, as this API will likely need to change before a new major release.

**Full Changelog**: [`v6.1.0...v6.1.1`](https://github.com/remix-run/react-router/compare/v6.1.0...v6.1.1)

[](#v610)
v6.1.0
----------------

Date: 2021-12-10

### [](#minor-changes-35)
Minor Changes

*   `<Outlet>` can now receive a `context` prop. This value is passed to child routes and is accessible via the new `useOutletContext` hook. See [the API docs](https://reactrouter.com/docs/en/v6/api#useoutletcontext)
     for details. ([#8461](https://github.com/remix-run/react-router/pull/8461)
    )
*   `<NavLink>` can now receive a child function for access to its props. ([#8164](https://github.com/remix-run/react-router/pull/8164)
    )
*   Improved TypeScript signature for `useMatch` and `matchPath`. For example, when you call `useMatch("foo/:bar/:baz")`, the path is parsed and the return type will be `PathMatch<"bar" | "baz">`. ([#8030](https://github.com/remix-run/react-router/pull/8030)
    )

### [](#patch-changes-76)
Patch Changes

*   Fixed a bug that broke support for base64 encoded IDs on nested routes ([#8291](https://github.com/remix-run/react-router/pull/8291)
    )
*   A few error message improvements ([#8202](https://github.com/remix-run/react-router/pull/8202)
    )

**Full Changelog**: [`v6.0.2...v6.1.0`](https://github.com/remix-run/react-router/compare/v6.0.2...v6.1.0)

[](#v602)
v6.0.2
----------------

Date: 2021-11-09

### [](#patch-changes-77)
Patch Changes

*   Added the `reloadDocument` prop to `<Link>`. This allows `<Link>` to function like a normal anchor tag by reloading the document after navigation while maintaining the relative `to` resolution ([#8283](https://github.com/remix-run/react-router/pull/8283)
    )

**Full Changelog**: [`v6.0.1...v6.0.2`](https://github.com/remix-run/react-router/compare/v6.0.1...v6.0.2)

[](#v601)
v6.0.1
----------------

Date: 2021-11-05

### [](#patch-changes-78)
Patch Changes

*   Add a default `<StaticRouter location>` value ([#8243](https://github.com/remix-run/react-router/pull/8243)
    )
*   Add invariant for using `<Route>` inside `<Routes>` to help people make the change ([#8238](https://github.com/remix-run/react-router/pull/8238)
    )

**Full Changelog**: [`v6.0.0...v6.0.1`](https://github.com/remix-run/react-router/compare/v6.0.0...v6.0.1)

[](#v600)
v6.0.0
----------------

Date: 2021-11-03

React Router v6 is here!

Please go read [our blog post for more information on all the great stuff in v6](https://remix.run/blog/react-router-v6)
 including [notes about how to upgrade from React Router v5](https://remix.run/blog/react-router-v6#upgrading-to-react-router-v6)
 and Reach Router.

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/CHANGELOG.md)

---

# Navigating  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/navigating)
[dev](/dev/start/framework/navigating)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Navigating

On this page

*   [Introduction](/start/framework/navigating#introduction)
    
*   [NavLink](/start/framework/navigating#navlink)
    
*   [Link](/start/framework/navigating#link)
    
*   [Form](/start/framework/navigating#form)
    
*   [redirect](/start/framework/navigating#redirect)
    
*   [useNavigate](/start/framework/navigating#usenavigate)
    

*   [Introduction](/start/framework/navigating#introduction)
    
*   [NavLink](/start/framework/navigating#navlink)
    
*   [Link](/start/framework/navigating#link)
    
*   [Form](/start/framework/navigating#form)
    
*   [redirect](/start/framework/navigating#redirect)
    
*   [useNavigate](/start/framework/navigating#usenavigate)
    

[](#navigating)
Navigating
==========================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

Users navigate your application with `<Link>`, `<NavLink>`, `<Form>`, `redirect`, and `useNavigate`.

[](#navlink)
NavLink
--------------------

This component is for navigation links that need to render active and pending states.

    import { NavLink } from "react-router";
    
    export function MyAppNav() {
      return (
        <nav>
          <NavLink to="/" end>
            Home
          </NavLink>
          <NavLink to="/trending" end>
            Trending Concerts
          </NavLink>
          <NavLink to="/concerts">All Concerts</NavLink>
          <NavLink to="/account">Account</NavLink>
        </nav>
      );
    }
    

`NavLink` renders default class names for different states for easy styling with CSS:

    a.active {
      color: red;
    }
    
    a.pending {
      animate: pulse 1s infinite;
    }
    
    a.transitioning {
      /* css transition is running */
    }
    

It also has callback props on `className`, `style`, and `children` with the states for inline styling or conditional rendering:

    // className
    <NavLink
      to="/messages"
      className={({ isActive, isPending, isTransitioning }) =>
        [\
          isPending ? "pending" : "",\
          isActive ? "active" : "",\
          isTransitioning ? "transitioning" : "",\
        ].join(" ")
      }
    >
      Messages
    </NavLink>
    

    // style
    <NavLink
      to="/messages"
      style={({ isActive, isPending, isTransitioning }) => {
        return {
          fontWeight: isActive ? "bold" : "",
          color: isPending ? "red" : "black",
          viewTransitionName: isTransitioning ? "slide" : "",
        };
      }}
    >
      Messages
    </NavLink>
    

    // children
    <NavLink to="/tasks">
      {({ isActive, isPending, isTransitioning }) => (
        <span className={isActive ? "active" : ""}>Tasks</span>
      )}
    </NavLink>
    

[](#link)
Link
--------------

Use `<Link>` when the link doesn't need active styling:

    import { Link } from "react-router";
    
    export function LoggedOutMessage() {
      return (
        <p>
          You've been logged out.{" "}
          <Link to="/login">Login again</Link>
        </p>
      );
    }
    

[](#form)
Form
--------------

The form component can be used to navigate with `URLSearchParams` provided by the user.

    <Form action="/search">
      <input type="text" name="q" />
    </Form>
    

If the user enters "journey" into the input and submits it, they will navigate to:

    /search?q=journey
    

Forms with `<Form method="post" />` will also navigate to the action prop but will submit the data as `FormData` instead of `URLSearchParams`. However, it is more common to `useFetcher()` to POST form data. See [Using Fetchers](../../how-to/fetchers)
.

[](#redirect)
redirect
----------------------

Inside of route loaders and actions, you can return a `redirect` to another URL.

    import { redirect } from "react-router";
    
    export async function loader({ request }) {
      let user = await getUser(request);
      if (!user) {
        return redirect("/login");
      }
      return { userName: user.name };
    }
    

It is common to redirect to a new record after it has been created:

    import { redirect } from "react-router";
    
    export async function action({ request }) {
      let formData = await request.formData();
      let project = await createProject(formData);
      return redirect(`/projects/${project.id}`);
    }
    

[](#usenavigate)
useNavigate
----------------------------

This hook allows the programmer to navigate the user to a new page without the user interacting. Usage of this hook should be uncommon. It's recommended to use the other APIs in this guide when possible.

Reserve usage of `useNavigate` to situations where the user is _not_ interacting but you need to navigate, for example:

*   Logging them out after inactivity
*   Timed UIs like quizzes, etc.

    import { useNavigate } from "react-router";
    
    export function useLogoutAfterInactivity() {
      let navigate = useNavigate();
    
      useFakeInactivityHook(() => {
        navigate("/logout");
      });
    }
    

* * *

Next: [Pending UI](./pending-ui)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/navigating.md)

---

# Pending UI  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/pending-ui)
[dev](/dev/start/framework/pending-ui)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Pending UI

On this page

*   [Introduction](/start/framework/pending-ui#introduction)
    
*   [Global Pending Navigation](/start/framework/pending-ui#global-pending-navigation)
    
*   [Local Pending Navigation](/start/framework/pending-ui#local-pending-navigation)
    
*   [Pending Form Submission](/start/framework/pending-ui#pending-form-submission)
    
*   [Optimistic UI](/start/framework/pending-ui#optimistic-ui)
    

*   [Introduction](/start/framework/pending-ui#introduction)
    
*   [Global Pending Navigation](/start/framework/pending-ui#global-pending-navigation)
    
*   [Local Pending Navigation](/start/framework/pending-ui#local-pending-navigation)
    
*   [Pending Form Submission](/start/framework/pending-ui#pending-form-submission)
    
*   [Optimistic UI](/start/framework/pending-ui#optimistic-ui)
    

[](#pending-ui)
Pending UI
==========================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

When the user navigates to a new route, or submits data to an action, the UI should immediately respond to the user's actions with a pending or optimistic state. Application code is responsible for this.

[](#global-pending-navigation)
Global Pending Navigation
--------------------------------------------------------

When the user navigates to a new url, the loaders for the next page are awaited before the next page renders. You can get the pending state from `useNavigation`.

    import { useNavigation } from "react-router";
    
    export default function Root() {
      const navigation = useNavigation();
      const isNavigating = Boolean(navigation.location);
    
      return (
        <html>
          <body>
            {isNavigating && <GlobalSpinner />}
            <Outlet />
          </body>
        </html>
      );
    }
    

[](#local-pending-navigation)
Local Pending Navigation
------------------------------------------------------

Pending indicators can also be localized to the link. NavLink's children, className, and style props can be functions that receive the pending state.

    import { NavLink } from "react-router";
    
    function Navbar() {
      return (
        <nav>
          <NavLink to="/home">
            {({ isPending }) => (
              <span>Home {isPending && <Spinner />}</span>
            )}
          </NavLink>
          <NavLink
            to="/about"
            style={({ isPending }) => ({
              color: isPending ? "gray" : "black",
            })}
          >
            About
          </NavLink>
        </nav>
      );
    }
    

[](#pending-form-submission)
Pending Form Submission
----------------------------------------------------

When a form is submitted, the UI should immediately respond to the user's actions with a pending state. This is easiest to do with a [fetcher](https://api.reactrouter.com/v7/functions/react_router.useFetcher.html)
 form because it has it's own independent state (whereas normal forms cause a global navigation).

    import { useFetcher } from "react-router";
    
    function NewProjectForm() {
      const fetcher = useFetcher();
    
      return (
        <fetcher.Form method="post">
          <input type="text" name="title" />
          <button type="submit">
            {fetcher.state !== "idle"
              ? "Submitting..."
              : "Submit"}
          </button>
        </fetcher.Form>
      );
    }
    

For non-fetcher form submissions, pending states are available on `useNavigation`.

    import { useNavigation, Form } from "react-router";
    
    function NewProjectForm() {
      const navigation = useNavigation();
    
      return (
        <Form method="post" action="/projects/new">
          <input type="text" name="title" />
          <button type="submit">
            {navigation.formAction === "/projects/new"
              ? "Submitting..."
              : "Submit"}
          </button>
        </Form>
      );
    }
    

[](#optimistic-ui)
Optimistic UI
--------------------------------

When the future state of the UI is known by the form submission data, an optimistic UI can be implemented for instant UX.

    function Task({ task }) {
      const fetcher = useFetcher();
    
      let isComplete = task.status === "complete";
      if (fetcher.formData) {
        isComplete =
          fetcher.formData.get("status") === "complete";
      }
    
      return (
        <div>
          <div>{task.title}</div>
          <fetcher.Form method="post">
            <button
              name="status"
              value={isComplete ? "incomplete" : "complete"}
            >
              {isComplete ? "Mark Incomplete" : "Mark Complete"}
            </button>
          </fetcher.Form>
        </div>
      );
    }
    

* * *

Next: [Testing](./testing)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/pending-ui.md)

---

# React Router Home (dev branch) | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

dev

Branches

[latest (7.6.0)](/home)
[dev](/dev/home)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/dev/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

React Router Home

[](#react-router-home)
React Router Home
========================================

React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. You can use it maximally as a React framework or as minimally as you want.

[](#getting-started)
Getting Started
------------------------------------

There are three primary ways, or "modes", to use it in your app, so there are three guides to get you started.

*   [Declarative](./start/declarative/installation)
    
*   [Data](./start/data/custom)
    
*   [Framework](./start/framework/installation)
    

Learn which mode is right for you in [Picking a Mode](./start/modes)
.

[](#using-these-guides)
Using These Guides
------------------------------------------

Across the docs you'll see the following icons:

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Available with Declarative")
    

These icons indicate which mode the content is relevant to.

Additional auto-generated reference documentation is available:

[Autogenerated Reference Docs ↗](https://api.reactrouter.com/v7/modules/react_router.html)

[](#upgrading)
Upgrading
------------------------

If you are caught up on future flags, upgrading from React Router v6 or Remix v2 is generally non-breaking. Remix v2 apps are encouraged to upgrade to React Router v7.

*   [Upgrade from v6](./upgrading/v6)
    
*   [Upgrade from Remix](./upgrading/remix)
    

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/dev/docs/index.md)

---

# Testing  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/testing)
[dev](/dev/start/framework/testing)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Testing

[](#testing)
Testing
====================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

When components use things like `useLoaderData`, `<Link>`, etc, they are required to be rendered in context of a React Router app. The `createRoutesStub` function creates that context to test components in isolation.

Consider a login form component that relies on `useActionData`

    import { useActionData } from "react-router";
    
    export function LoginForm() {
      const { errors } = useActionData();
      return (
        <Form method="post">
          <label>
            <input type="text" name="username" />
            {errors?.username && <div>{errors.username}</div>}
          </label>
    
          <label>
            <input type="password" name="password" />
            {errors?.password && <div>{errors.password}</div>}
          </label>
    
          <button type="submit">Login</button>
        </Form>
      );
    }
    

We can test this component with `createRoutesStub`. It takes an array of objects that resemble route modules with loaders, actions, and components.

    import { createRoutesStub } from "react-router";
    import {
      render,
      screen,
      waitFor,
    } from "@testing-library/react";
    import userEvent from "@testing-library/user-event";
    import { LoginForm } from "./LoginForm";
    
    test("LoginForm renders error messages", async () => {
      const USER_MESSAGE = "Username is required";
      const PASSWORD_MESSAGE = "Password is required";
    
      const Stub = createRoutesStub([\
        {\
          path: "/login",\
          Component: LoginForm,\
          action() {\
            return {\
              errors: {\
                username: USER_MESSAGE,\
                password: PASSWORD_MESSAGE,\
              },\
            };\
          },\
        },\
      ]);
    
      // render the app stub at "/login"
      render(<Stub initialEntries={["/login"]} />);
    
      // simulate interactions
      userEvent.click(screen.getByText("Login"));
      await waitFor(() => screen.findByText(USER_MESSAGE));
      await waitFor(() => screen.findByText(PASSWORD_MESSAGE));
    });
    

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/testing.md)

---

# Deploying  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/framework/deploying)
[dev](/dev/start/framework/deploying)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Deploying

On this page

*   [Introduction](/start/framework/deploying#introduction)
    
*   [Templates](/start/framework/deploying#templates)
    
*   [Node.js with Docker](/start/framework/deploying#nodejs-with-docker)
    
*   [Node with Docker (Custom Server)](/start/framework/deploying#node-with-docker-custom-server)
    
*   [Node with Docker and Postgres](/start/framework/deploying#node-with-docker-and-postgres)
    
*   [Vercel](/start/framework/deploying#vercel)
    
*   [Cloudflare Workers w/ D1](/start/framework/deploying#cloudflare-workers-w-d1)
    
*   [Cloudflare Workers](/start/framework/deploying#cloudflare-workers)
    
*   [Netlify](/start/framework/deploying#netlify)
    

*   [Introduction](/start/framework/deploying#introduction)
    
*   [Templates](/start/framework/deploying#templates)
    
*   [Node.js with Docker](/start/framework/deploying#nodejs-with-docker)
    
*   [Node with Docker (Custom Server)](/start/framework/deploying#node-with-docker-custom-server)
    
*   [Node with Docker and Postgres](/start/framework/deploying#node-with-docker-and-postgres)
    
*   [Vercel](/start/framework/deploying#vercel)
    
*   [Cloudflare Workers w/ D1](/start/framework/deploying#cloudflare-workers-w-d1)
    
*   [Cloudflare Workers](/start/framework/deploying#cloudflare-workers)
    
*   [Netlify](/start/framework/deploying#netlify)
    

[](#deploying)
Deploying
========================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#introduction)
Introduction
------------------------------

React Router can be deployed two ways:

*   Fullstack Hosting
*   Static Hosting

The official [React Router templates](https://github.com/remix-run/react-router-templates)
 can help you bootstrap an application or be used as a reference for your own application.

When deploying to static hosting, you can deploy React Router the same as any other single page application with React.

[](#templates)
Templates
------------------------

After running the `create-react-router` command, make sure to follow the instructions in the README.

### [](#nodejs-with-docker)
Node.js with Docker

    npx create-react-router@latest --template remix-run/react-router-templates/default
    

*   Server Rendering
*   Tailwind CSS

The containerized application can be deployed to any platform that supports Docker, including:

*   AWS ECS
*   Google Cloud Run
*   Azure Container Apps
*   Digital Ocean App Platform
*   Fly.io
*   Railway

### [](#node-with-docker-custom-server)
Node with Docker (Custom Server)

    npx create-react-router@latest --template remix-run/react-router-templates/node-custom-server
    

*   Server Rendering
*   Tailwind CSS
*   Custom express server for more control

The containerized application can be deployed to any platform that supports Docker, including:

*   AWS ECS
*   Google Cloud Run
*   Azure Container Apps
*   Digital Ocean App Platform
*   Fly.io
*   Railway

### [](#node-with-docker-and-postgres)
Node with Docker and Postgres

    npx create-react-router@latest --template remix-run/react-router-templates/node-postgres
    

*   Server Rendering
*   Postgres Database with Drizzle
*   Tailwind CSS
*   Custom express server for more control

The containerized application can be deployed to any platform that supports Docker, including:

*   AWS ECS
*   Google Cloud Run
*   Azure Container Apps
*   Digital Ocean App Platform
*   Fly.io
*   Railway

### [](#vercel)
Vercel

    npx create-react-router@latest --template remix-run/react-router-templates/vercel
    

*   Server Rendering
*   Tailwind CSS

### [](#cloudflare-workers-w-d1)
Cloudflare Workers w/ D1

    npx create-react-router@latest --template remix-run/react-router-templates/cloudflare-d1
    

*   Server Rendering
*   D1 Database with Drizzle ORM
*   Tailwind CSS

### [](#cloudflare-workers)
Cloudflare Workers

    npx create-react-router@latest --template remix-run/react-router-templates/cloudflare
    

*   Server Rendering
*   Tailwind CSS

### [](#netlify)
Netlify

    npx create-react-router@latest --template remix-run/react-router-templates/netlify
    

*   Server Rendering
*   Tailwind CSS

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/framework/deploying.md)

---

# Installation  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/data/installation)
[dev](/dev/start/data/installation)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Installation

[](#installation)
Installation
==============================

*   [Framework](../../start/modes "Not available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#bootstrap-with-a-bundler-template)
Bootstrap with a Bundler Template
------------------------------------------------------------------------

You can start with a React template from Vite and choose "React", otherwise bootstrap your application however you prefer (Parcel, Webpack, etc).

    npx create-vite@latest
    

[](#install-react-router)
Install React Router
----------------------------------------------

Next install React Router from npm:

    npm i react-router
    

[](#create-a-router-and-render)
Create a Router and Render
----------------------------------------------------------

Create a router and pass it to `RouterProvider`:

    import {
      createBrowserRouter,
      RouterProvider,
    } from "react-router";
    
    import React from "react";
    import ReactDOM from "react-dom/client";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <div>Hello World</div>,\
      },\
    ]);
    
    const root = document.getElementById("root");
    
    ReactDOM.createRoot(root).render(
      <RouterProvider router={router} />
    );
    

* * *

Next: [Routing](./routing)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/data/installation.md)

---

# Routing  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/data/routing)
[dev](/dev/start/data/routing)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Routing

On this page

*   [Configuring Routes](/start/data/routing#configuring-routes)
    
*   [Route Objects](/start/data/routing#route-objects)
    
*   [Nested Routes](/start/data/routing#nested-routes)
    
*   [Layout Routes](/start/data/routing#layout-routes)
    
*   [Index Routes](/start/data/routing#index-routes)
    
*   [Prefix Route](/start/data/routing#prefix-route)
    
*   [Dynamic Segments](/start/data/routing#dynamic-segments)
    
*   [Optional Segments](/start/data/routing#optional-segments)
    
*   [Splats](/start/data/routing#splats)
    

*   [Configuring Routes](/start/data/routing#configuring-routes)
    
*   [Route Objects](/start/data/routing#route-objects)
    
*   [Nested Routes](/start/data/routing#nested-routes)
    
*   [Layout Routes](/start/data/routing#layout-routes)
    
*   [Index Routes](/start/data/routing#index-routes)
    
*   [Prefix Route](/start/data/routing#prefix-route)
    
*   [Dynamic Segments](/start/data/routing#dynamic-segments)
    
*   [Optional Segments](/start/data/routing#optional-segments)
    
*   [Splats](/start/data/routing#splats)
    

[](#routing)
Routing
====================

*   [Framework](../../start/modes "Not available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#configuring-routes)
Configuring Routes
------------------------------------------

Routes are configured as the first argument to `createBrowserRouter`. At a minimum, you need a path and component:

    import { createBrowserRouter } from "react-router";
    
    function Root() {
      return <h1>Hello world</h1>;
    }
    
    const router = createBrowserRouter([\
      { path: "/", Component: Root },\
    ]);
    

Here is a larger sample route config:

    createBrowserRouter([\
      {\
        path: "/",\
        Component: Root,\
        children: [\
          { index: true, Component: Home },\
          { path: "about", Component: About },\
          {\
            path: "auth",\
            Component: AuthLayout,\
            children: [\
              { path: "login", Component: Login },\
              { path: "register", Component: Register },\
            ],\
          },\
          {\
            path: "concerts",\
            children: [\
              { index: true, Component: ConcertsHome },\
              { path: ":city", Component: ConcertsCity },\
              { path: "trending", Component: ConcertsTrending },\
            ],\
          },\
        ],\
      },\
    ]);
    

[](#route-objects)
Route Objects
--------------------------------

Route objects define the behavior of a route beyond just the path and component, like data loading and actions. We'll go into more detail in the [Route Object guide](./route-object)
, but here's a quick example of a loader.

    import {
      createBrowserRouter,
      useLoaderData,
    } from "react-router";
    
    createBrowserRouter([\
      {\
        path: "/teams/:teamId",\
        loader: async ({ params }) => {\
          let team = await fetchTeam(params.teamId);\
          return { name: team.name };\
        },\
        Component: Team,\
      },\
    ]);
    
    function Team() {
      let data = useLoaderData();
      return <h1>{data.name}</h1>;
    }
    

[](#nested-routes)
Nested Routes
--------------------------------

Routes can be nested inside parent routes through `children`.

    createBrowserRouter([\
      {\
        path: "/dashboard",\
        Component: Dashboard,\
        children: [\
          { index: true, Component: Home },\
          { path: "settings", Component: Settings },\
        ],\
      },\
    ]);
    

The path of the parent is automatically included in the child, so this config creates both `"/dashboard"` and `"/dashboard/settings"` URLs.

Child routes are rendered through the `<Outlet/>` in the parent route.

    import { Outlet } from "react-router";
    
    export default function Dashboard() {
      return (
        <div>
          <h1>Dashboard</h1>
          {/* will either be <Home> or <Settings> */}
          <Outlet />
        </div>
      );
    }
    

[](#layout-routes)
Layout Routes
--------------------------------

Omitting the `path` in a route creates new [Nested Routes](#nested-routes)
 for its children without adding any segments to the URL.

    createBrowserRouter([\
      {\
        // no path on this parent route, just the component\
        Component: MarketingLayout,\
        children: [\
          { index: true, Component: Home },\
          { path: "contact", Component: Contact },\
        ],\
      },\
    \
      {\
        path: "projects",\
        children: [\
          { index: true, Component: ProjectsHome },\
          {\
            // again, no path, just a component for the layout\
            Component: ProjectLayout,\
            children: [\
              { path: ":pid", Component: Project },\
              { path: ":pid/edit", Component: EditProject },\
            ],\
          },\
        ],\
      },\
    ]);
    

Note that:

*   `Home` and `Contact` will be rendered into the `MarketingLayout` outlet
*   `Project` and `EditProject` will be rendered into the `ProjectLayout` outlet while `ProjectsHome` will not.

[](#index-routes)
Index Routes
------------------------------

Index routes are defined by setting `index: true` on a route object without a path.

    { index: true, Component: Home }
    

Index routes render into their parent's [Outlet](https://api.reactrouter.com/v7/functions/react_router.Outlet.html)
 at their parent's URL (like a default child route).

    import { createBrowserRouter } from "react-router";
    
    createBrowserRouter([\
      // renders at "/"\
      { index: true, Component: Home },\
      {\
        Component: Dashboard,\
        path: "/dashboard",\
        children: [\
          // renders at "/dashboard"\
          { index: true, Component: DashboardHome },\
          { path: "settings", Component: DashboardSettings },\
        ],\
      },\
    ]);
    

Note that index routes can't have children.

[](#prefix-route)
Prefix Route
------------------------------

A route with just a path and no component creates a group of routes with a path prefix.

    createBrowserRouter([\
      {\
        // no component, just a path\
        path: "/projects",\
        children: [\
          { index: true, Component: ProjectsHome },\
          { path: ":pid", Component: Project },\
          { path: ":pid/edit", Component: EditProject },\
        ],\
      },\
    ]);
    

This creates the routes `/projects`, `/projects/:pid`, and `/projects/:pid/edit` without introducing a layout component.

[](#dynamic-segments)
Dynamic Segments
--------------------------------------

If a path segment starts with `:` then it becomes a "dynamic segment". When the route matches the URL, the dynamic segment will be parsed from the URL and provided as `params` to other router APIs.

    {
      path: "teams/:teamId",
      loader: async ({ params }) => {
        // params are available in loaders/actions
        let team = await fetchTeam(params.teamId);
        return { name: team.name };
      },
      Component: Team,
    }
    

    import { useParams } from "react-router";
    
    function Team() {
      // params are available in components through useParams
      let params = useParams();
      // ...
    }
    

You can have multiple dynamic segments in one route path:

    {
      path: "c/:categoryId/p/:productId";
    }
    

[](#optional-segments)
Optional Segments
----------------------------------------

You can make a route segment optional by adding a `?` to the end of the segment.

    {
      path: ":lang?/categories";
    }
    

You can have optional static segments, too:

    {
      path: "users/:userId/edit?";
    }
    

[](#splats)
Splats
------------------

Also known as "catchall" and "star" segments. If a route path pattern ends with `/*` then it will match any characters following the `/`, including other `/` characters.

    {
      path: "files/*";
      loader: async ({ params }) => {
        params["*"]; // will contain the remaining URL after files/
      };
    }
    

You can destructure the `*`, you just have to assign it a new name. A common name is `splat`:

    const { "*": splat } = params;
    

* * *

Next: [Route Object](./route-object)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/data/routing.md)

---

# CHANGELOG.md v7.6.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

7.6.0

Branches

[latest (7.6.0)](/changelog)
[dev](/dev/changelog)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

CHANGELOG.md

On this page

*   [v7.6.0](/7.6.0/changelog#v760)
    
*   [What's Changed](/7.6.0/changelog#whats-changed)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package)
    
*   [v7.5.3](/7.6.0/changelog#v753)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-1)
    
*   [v7.5.2](/7.6.0/changelog#v752)
    
*   [Security Notice](/7.6.0/changelog#security-notice)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-2)
    
*   [v7.5.1](/7.6.0/changelog#v751)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-3)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-1)
    
*   [v7.5.0](/7.6.0/changelog#v750)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-1)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-1)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-4)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-2)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-1)
    
*   [v7.4.1](/7.6.0/changelog#v741)
    
*   [Security Notice](/7.6.0/changelog#security-notice-1)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-5)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-3)
    
*   [v7.4.0](/7.6.0/changelog#v740)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-2)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-6)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-4)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-2)
    
*   [v7.3.0](/7.6.0/changelog#v730)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-3)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-7)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-5)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-3)
    
*   [v7.2.0](/7.6.0/changelog#v720)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-2)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-4)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-8)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-6)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-4)
    
*   [v7.1.5](/7.6.0/changelog#v715)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-9)
    
*   [v7.1.4](/7.6.0/changelog#v714)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-10)
    
*   [v7.1.3](/7.6.0/changelog#v713)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-11)
    
*   [v7.1.2](/7.6.0/changelog#v712)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-12)
    
*   [v7.1.1](/7.6.0/changelog#v711)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-13)
    
*   [v7.1.0](/7.6.0/changelog#v710)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-5)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-14)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-5)
    
*   [v7.0.2](/7.6.0/changelog#v702)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-15)
    
*   [v7.0.1](/7.6.0/changelog#v701)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-16)
    
*   [v7.0.0](/7.6.0/changelog#v700)
    
*   [Breaking Changes](/7.6.0/changelog#breaking-changes)
    
*   [Other Notable Changes](/7.6.0/changelog#other-notable-changes)
    
*   [Major Changes (`react-router`)](/7.6.0/changelog#major-changes-react-router)
    
*   [Major Changes (`@react-router/*`)](/7.6.0/changelog#major-changes-react-router-1)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-6)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-17)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-6)
    
*   [v6.30.0](/7.6.0/changelog#v6300)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-7)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-18)
    
*   [v6.29.0](/7.6.0/changelog#v6290)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-8)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-19)
    
*   [v6.28.2](/7.6.0/changelog#v6282)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-20)
    
*   [v6.28.1](/7.6.0/changelog#v6281)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-21)
    
*   [v6.28.0](/7.6.0/changelog#v6280)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-3)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-9)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-22)
    
*   [v6.27.0](/7.6.0/changelog#v6270)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-4)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-10)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-23)
    
*   [v6.26.2](/7.6.0/changelog#v6262)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-24)
    
*   [v6.26.1](/7.6.0/changelog#v6261)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-25)
    
*   [v6.26.0](/7.6.0/changelog#v6260)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-11)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-26)
    
*   [v6.25.1](/7.6.0/changelog#v6251)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-27)
    
*   [v6.25.0](/7.6.0/changelog#v6250)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-5)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-12)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-28)
    
*   [v6.24.1](/7.6.0/changelog#v6241)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-29)
    
*   [v6.24.0](/7.6.0/changelog#v6240)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-6)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-13)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-30)
    
*   [v6.23.1](/7.6.0/changelog#v6231)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-31)
    
*   [v6.23.0](/7.6.0/changelog#v6230)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-7)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-14)
    
*   [v6.22.3](/7.6.0/changelog#v6223)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-32)
    
*   [v6.22.2](/7.6.0/changelog#v6222)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-33)
    
*   [v6.22.1](/7.6.0/changelog#v6221)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-34)
    
*   [v6.22.0](/7.6.0/changelog#v6220)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-8)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-15)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-35)
    
*   [v6.21.3](/7.6.0/changelog#v6213)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-36)
    
*   [v6.21.2](/7.6.0/changelog#v6212)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-37)
    
*   [v6.21.1](/7.6.0/changelog#v6211)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-38)
    
*   [v6.21.0](/7.6.0/changelog#v6210)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-9)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-16)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-39)
    
*   [v6.20.1](/7.6.0/changelog#v6201)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-40)
    
*   [v6.20.0](/7.6.0/changelog#v6200)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-17)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-41)
    
*   [v6.19.0](/7.6.0/changelog#v6190)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-10)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-18)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-42)
    
*   [v6.18.0](/7.6.0/changelog#v6180)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-11)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-19)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-43)
    
*   [v6.17.0](/7.6.0/changelog#v6170)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-12)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-20)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-44)
    
*   [v6.16.0](/7.6.0/changelog#v6160)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-21)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-45)
    
*   [v6.15.0](/7.6.0/changelog#v6150)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-22)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-46)
    
*   [v6.14.2](/7.6.0/changelog#v6142)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-47)
    
*   [v6.14.1](/7.6.0/changelog#v6141)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-48)
    
*   [v6.14.0](/7.6.0/changelog#v6140)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-13)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-23)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-49)
    
*   [v6.13.0](/7.6.0/changelog#v6130)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-14)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-24)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-50)
    
*   [v6.12.1](/7.6.0/changelog#v6121)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-51)
    
*   [v6.12.0](/7.6.0/changelog#v6120)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-15)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-25)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-52)
    
*   [v6.11.2](/7.6.0/changelog#v6112)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-53)
    
*   [v6.11.1](/7.6.0/changelog#v6111)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-54)
    
*   [v6.11.0](/7.6.0/changelog#v6110)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-26)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-55)
    
*   [v6.10.0](/7.6.0/changelog#v6100)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-16)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-27)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-56)
    
*   [v6.9.0](/7.6.0/changelog#v690)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-17)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-28)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-57)
    
*   [v6.8.2](/7.6.0/changelog#v682)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-58)
    
*   [v6.8.1](/7.6.0/changelog#v681)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-59)
    
*   [v6.8.0](/7.6.0/changelog#v680)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-29)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-60)
    
*   [v6.7.0](/7.6.0/changelog#v670)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-30)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-61)
    
*   [v6.6.2](/7.6.0/changelog#v662)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-62)
    
*   [v6.6.1](/7.6.0/changelog#v661)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-63)
    
*   [v6.6.0](/7.6.0/changelog#v660)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-18)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-31)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-64)
    
*   [v6.5.0](/7.6.0/changelog#v650)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-19)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-32)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-65)
    
*   [v6.4.5](/7.6.0/changelog#v645)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-66)
    
*   [v6.4.4](/7.6.0/changelog#v644)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-67)
    
*   [v6.4.3](/7.6.0/changelog#v643)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-68)
    
*   [v6.4.2](/7.6.0/changelog#v642)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-69)
    
*   [v6.4.1](/7.6.0/changelog#v641)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-70)
    
*   [v6.4.0](/7.6.0/changelog#v640)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-20)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-71)
    
*   [v6.3.0](/7.6.0/changelog#v630)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-33)
    
*   [v6.2.2](/7.6.0/changelog#v622)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-72)
    
*   [v6.2.1](/7.6.0/changelog#v621)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-73)
    
*   [v6.2.0](/7.6.0/changelog#v620)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-34)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-74)
    
*   [v6.1.1](/7.6.0/changelog#v611)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-75)
    
*   [v6.1.0](/7.6.0/changelog#v610)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-35)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-76)
    
*   [v6.0.2](/7.6.0/changelog#v602)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-77)
    
*   [v6.0.1](/7.6.0/changelog#v601)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-78)
    
*   [v6.0.0](/7.6.0/changelog#v600)
    

*   [v7.6.0](/7.6.0/changelog#v760)
    
*   [What's Changed](/7.6.0/changelog#whats-changed)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package)
    
*   [v7.5.3](/7.6.0/changelog#v753)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-1)
    
*   [v7.5.2](/7.6.0/changelog#v752)
    
*   [Security Notice](/7.6.0/changelog#security-notice)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-2)
    
*   [v7.5.1](/7.6.0/changelog#v751)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-3)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-1)
    
*   [v7.5.0](/7.6.0/changelog#v750)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-1)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-1)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-4)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-2)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-1)
    
*   [v7.4.1](/7.6.0/changelog#v741)
    
*   [Security Notice](/7.6.0/changelog#security-notice-1)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-5)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-3)
    
*   [v7.4.0](/7.6.0/changelog#v740)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-2)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-6)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-4)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-2)
    
*   [v7.3.0](/7.6.0/changelog#v730)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-3)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-7)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-5)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-3)
    
*   [v7.2.0](/7.6.0/changelog#v720)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-2)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-4)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-8)
    
*   [Unstable Changes](/7.6.0/changelog#unstable-changes-6)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-4)
    
*   [v7.1.5](/7.6.0/changelog#v715)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-9)
    
*   [v7.1.4](/7.6.0/changelog#v714)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-10)
    
*   [v7.1.3](/7.6.0/changelog#v713)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-11)
    
*   [v7.1.2](/7.6.0/changelog#v712)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-12)
    
*   [v7.1.1](/7.6.0/changelog#v711)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-13)
    
*   [v7.1.0](/7.6.0/changelog#v710)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-5)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-14)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-5)
    
*   [v7.0.2](/7.6.0/changelog#v702)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-15)
    
*   [v7.0.1](/7.6.0/changelog#v701)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-16)
    
*   [v7.0.0](/7.6.0/changelog#v700)
    
*   [Breaking Changes](/7.6.0/changelog#breaking-changes)
    
*   [Other Notable Changes](/7.6.0/changelog#other-notable-changes)
    
*   [Major Changes (`react-router`)](/7.6.0/changelog#major-changes-react-router)
    
*   [Major Changes (`@react-router/*`)](/7.6.0/changelog#major-changes-react-router-1)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-6)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-17)
    
*   [Changes by Package](/7.6.0/changelog#changes-by-package-6)
    
*   [v6.30.0](/7.6.0/changelog#v6300)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-7)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-18)
    
*   [v6.29.0](/7.6.0/changelog#v6290)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-8)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-19)
    
*   [v6.28.2](/7.6.0/changelog#v6282)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-20)
    
*   [v6.28.1](/7.6.0/changelog#v6281)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-21)
    
*   [v6.28.0](/7.6.0/changelog#v6280)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-3)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-9)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-22)
    
*   [v6.27.0](/7.6.0/changelog#v6270)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-4)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-10)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-23)
    
*   [v6.26.2](/7.6.0/changelog#v6262)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-24)
    
*   [v6.26.1](/7.6.0/changelog#v6261)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-25)
    
*   [v6.26.0](/7.6.0/changelog#v6260)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-11)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-26)
    
*   [v6.25.1](/7.6.0/changelog#v6251)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-27)
    
*   [v6.25.0](/7.6.0/changelog#v6250)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-5)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-12)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-28)
    
*   [v6.24.1](/7.6.0/changelog#v6241)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-29)
    
*   [v6.24.0](/7.6.0/changelog#v6240)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-6)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-13)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-30)
    
*   [v6.23.1](/7.6.0/changelog#v6231)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-31)
    
*   [v6.23.0](/7.6.0/changelog#v6230)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-7)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-14)
    
*   [v6.22.3](/7.6.0/changelog#v6223)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-32)
    
*   [v6.22.2](/7.6.0/changelog#v6222)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-33)
    
*   [v6.22.1](/7.6.0/changelog#v6221)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-34)
    
*   [v6.22.0](/7.6.0/changelog#v6220)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-8)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-15)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-35)
    
*   [v6.21.3](/7.6.0/changelog#v6213)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-36)
    
*   [v6.21.2](/7.6.0/changelog#v6212)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-37)
    
*   [v6.21.1](/7.6.0/changelog#v6211)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-38)
    
*   [v6.21.0](/7.6.0/changelog#v6210)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-9)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-16)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-39)
    
*   [v6.20.1](/7.6.0/changelog#v6201)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-40)
    
*   [v6.20.0](/7.6.0/changelog#v6200)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-17)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-41)
    
*   [v6.19.0](/7.6.0/changelog#v6190)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-10)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-18)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-42)
    
*   [v6.18.0](/7.6.0/changelog#v6180)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-11)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-19)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-43)
    
*   [v6.17.0](/7.6.0/changelog#v6170)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-12)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-20)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-44)
    
*   [v6.16.0](/7.6.0/changelog#v6160)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-21)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-45)
    
*   [v6.15.0](/7.6.0/changelog#v6150)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-22)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-46)
    
*   [v6.14.2](/7.6.0/changelog#v6142)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-47)
    
*   [v6.14.1](/7.6.0/changelog#v6141)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-48)
    
*   [v6.14.0](/7.6.0/changelog#v6140)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-13)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-23)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-49)
    
*   [v6.13.0](/7.6.0/changelog#v6130)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-14)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-24)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-50)
    
*   [v6.12.1](/7.6.0/changelog#v6121)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-51)
    
*   [v6.12.0](/7.6.0/changelog#v6120)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-15)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-25)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-52)
    
*   [v6.11.2](/7.6.0/changelog#v6112)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-53)
    
*   [v6.11.1](/7.6.0/changelog#v6111)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-54)
    
*   [v6.11.0](/7.6.0/changelog#v6110)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-26)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-55)
    
*   [v6.10.0](/7.6.0/changelog#v6100)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-16)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-27)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-56)
    
*   [v6.9.0](/7.6.0/changelog#v690)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-17)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-28)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-57)
    
*   [v6.8.2](/7.6.0/changelog#v682)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-58)
    
*   [v6.8.1](/7.6.0/changelog#v681)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-59)
    
*   [v6.8.0](/7.6.0/changelog#v680)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-29)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-60)
    
*   [v6.7.0](/7.6.0/changelog#v670)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-30)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-61)
    
*   [v6.6.2](/7.6.0/changelog#v662)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-62)
    
*   [v6.6.1](/7.6.0/changelog#v661)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-63)
    
*   [v6.6.0](/7.6.0/changelog#v660)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-18)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-31)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-64)
    
*   [v6.5.0](/7.6.0/changelog#v650)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-19)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-32)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-65)
    
*   [v6.4.5](/7.6.0/changelog#v645)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-66)
    
*   [v6.4.4](/7.6.0/changelog#v644)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-67)
    
*   [v6.4.3](/7.6.0/changelog#v643)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-68)
    
*   [v6.4.2](/7.6.0/changelog#v642)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-69)
    
*   [v6.4.1](/7.6.0/changelog#v641)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-70)
    
*   [v6.4.0](/7.6.0/changelog#v640)
    
*   [What's Changed](/7.6.0/changelog#whats-changed-20)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-71)
    
*   [v6.3.0](/7.6.0/changelog#v630)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-33)
    
*   [v6.2.2](/7.6.0/changelog#v622)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-72)
    
*   [v6.2.1](/7.6.0/changelog#v621)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-73)
    
*   [v6.2.0](/7.6.0/changelog#v620)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-34)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-74)
    
*   [v6.1.1](/7.6.0/changelog#v611)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-75)
    
*   [v6.1.0](/7.6.0/changelog#v610)
    
*   [Minor Changes](/7.6.0/changelog#minor-changes-35)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-76)
    
*   [v6.0.2](/7.6.0/changelog#v602)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-77)
    
*   [v6.0.1](/7.6.0/changelog#v601)
    
*   [Patch Changes](/7.6.0/changelog#patch-changes-78)
    
*   [v6.0.0](/7.6.0/changelog#v600)
    

[](#react-router-releases)
React Router Releases
================================================

This page lists all releases/release notes for React Router back to `v6.0.0`. For releases prior to v6, please refer to the [Github Releases Page](https://github.com/remix-run/react-router/releases)
.

We manage release notes in this file instead of the paginated Github Releases Page for 2 reasons:

*   Pagination in the Github UI means that you cannot easily search release notes for a large span of releases at once
*   The paginated Github interface also cuts off longer releases notes without indication in list view, and you need to click into the detail view to see the full set of release notes

Table of Contents

*   [React Router Releases](#react-router-releases)
    *   [v7.6.0](#v760)
        *   [What's Changed](#whats-changed)
            *   [`routeDiscovery` Config Option](#routediscovery-config-option)
                
            *   [Automatic Types for Future Flags](#automatic-types-for-future-flags)
                
        *   [Minor Changes](#minor-changes)
            
        *   [Patch Changes](#patch-changes)
            
        *   [Unstable Changes](#unstable-changes)
            
        *   [Changes by Package](#changes-by-package)
            
    *   [v7.5.3](#v753)
        *   [Patch Changes](#patch-changes-1)
            
    *   [v7.5.2](#v752)
        *   [Security Notice](#security-notice)
            
        *   [Patch Changes](#patch-changes-2)
            
    *   [v7.5.1](#v751)
        *   [Patch Changes](#patch-changes-3)
            
        *   [Unstable Changes](#unstable-changes-1)
            
    *   [v7.5.0](#v750)
        *   [What's Changed](#whats-changed-1)
            *   [`route.lazy` Object API](#routelazy-object-api)
                
        *   [Minor Changes](#minor-changes-1)
            
        *   [Patch Changes](#patch-changes-4)
            
        *   [Unstable Changes](#unstable-changes-2)
            
        *   [Changes by Package](#changes-by-package-1)
            
    *   [v7.4.1](#v741)
        *   [Security Notice](#security-notice-1)
            
        *   [Patch Changes](#patch-changes-5)
            
        *   [Unstable Changes](#unstable-changes-3)
            
    *   [v7.4.0](#v740)
        *   [Minor Changes](#minor-changes-2)
            
        *   [Patch Changes](#patch-changes-6)
            
        *   [Unstable Changes](#unstable-changes-4)
            
        *   [Changes by Package](#changes-by-package-2)
            
    *   [v7.3.0](#v730)
        *   [Minor Changes](#minor-changes-3)
            
        *   [Patch Changes](#patch-changes-7)
            
        *   [Unstable Changes](#unstable-changes-5)
            *   [Client-side `context` (unstable)](#client-side-context-unstable)
                
            *   [Middleware (unstable)](#middleware-unstable)
                *   [Middleware `context` parameter](#middleware-context-parameter)
                    
            *   [`unstable_SerializesTo`](#unstable_serializesto)
                
        *   [Changes by Package](#changes-by-package-3)
            
    *   [v7.2.0](#v720)
        *   [What's Changed](#whats-changed-2)
            *   [Type-safe `href` utility](#type-safe-href-utility)
                
            *   [Prerendering with a SPA Fallback](#prerendering-with-a-spa-fallback)
                
            *   [Allow a root `loader` in SPA Mode](#allow-a-root-loader-in-spa-mode)
                
        *   [Minor Changes](#minor-changes-4)
            
        *   [Patch Changes](#patch-changes-8)
            
        *   [Unstable Changes](#unstable-changes-6)
            *   [Split Route Modules (unstable)](#split-route-modules-unstable)
                
        *   [Changes by Package](#changes-by-package-4)
            
    *   [v7.1.5](#v715)
        *   [Patch Changes](#patch-changes-9)
            
    *   [v7.1.4](#v714)
        *   [Patch Changes](#patch-changes-10)
            
    *   [v7.1.3](#v713)
        *   [Patch Changes](#patch-changes-11)
            
    *   [v7.1.2](#v712)
        *   [Patch Changes](#patch-changes-12)
            
    *   [v7.1.1](#v711)
        *   [Patch Changes](#patch-changes-13)
            
    *   [v7.1.0](#v710)
        *   [Minor Changes](#minor-changes-5)
            
        *   [Patch Changes](#patch-changes-14)
            
        *   [Changes by Package](#changes-by-package-5)
            
    *   [v7.0.2](#v702)
        *   [Patch Changes](#patch-changes-15)
            
    *   [v7.0.1](#v701)
        *   [Patch Changes](#patch-changes-16)
            
    *   [v7.0.0](#v700)
        *   [Breaking Changes](#breaking-changes)
            *   [Package Restructuring](#package-restructuring)
                
            *   [Removed Adapter Re-exports](#removed-adapter-re-exports)
                
            *   [Removed APIs](#removed-apis)
                
            *   [Minimum Versions](#minimum-versions)
                
            *   [Adopted Future Flag Behaviors](#adopted-future-flag-behaviors)
                
            *   [Vite Compiler](#vite-compiler)
                
            *   [Exposed Router Promises](#exposed-router-promises)
                
        *   [Other Notable Changes](#other-notable-changes)
            *   [`routes.ts`](#routests)
                
            *   [Typesafety improvements](#typesafety-improvements)
                
            *   [Prerendering](#prerendering)
                
        *   [Major Changes (`react-router`)](#major-changes-react-router)
            
        *   [Major Changes (`@react-router/*`)](#major-changes-react-router-1)
            
        *   [Minor Changes](#minor-changes-6)
            
        *   [Patch Changes](#patch-changes-17)
            
        *   [Changes by Package](#changes-by-package-6)
            
*   [React Router v6 Releases](#react-router-v6-releases)
    *   [v6.30.0](#v6300)
        *   [Minor Changes](#minor-changes-7)
            
        *   [Patch Changes](#patch-changes-18)
            
    *   [v6.29.0](#v6290)
        *   [Minor Changes](#minor-changes-8)
            
        *   [Patch Changes](#patch-changes-19)
            
    *   [v6.28.2](#v6282)
        *   [Patch Changes](#patch-changes-20)
            
    *   [v6.28.1](#v6281)
        *   [Patch Changes](#patch-changes-21)
            
    *   [v6.28.0](#v6280)
        *   [What's Changed](#whats-changed-3)
            
        *   [Minor Changes](#minor-changes-9)
            
        *   [Patch Changes](#patch-changes-22)
            
    *   [v6.27.0](#v6270)
        *   [What's Changed](#whats-changed-4)
            *   [Stabilized APIs](#stabilized-apis)
                
        *   [Minor Changes](#minor-changes-10)
            
        *   [Patch Changes](#patch-changes-23)
            
    *   [v6.26.2](#v6262)
        *   [Patch Changes](#patch-changes-24)
            
    *   [v6.26.1](#v6261)
        *   [Patch Changes](#patch-changes-25)
            
    *   [v6.26.0](#v6260)
        *   [Minor Changes](#minor-changes-11)
            
        *   [Patch Changes](#patch-changes-26)
            
    *   [v6.25.1](#v6251)
        *   [Patch Changes](#patch-changes-27)
            
    *   [v6.25.0](#v6250)
        *   [What's Changed](#whats-changed-5)
            *   [Stabilized `v7_skipActionErrorRevalidation`](#stabilized-v7_skipactionerrorrevalidation)
                
        *   [Minor Changes](#minor-changes-12)
            
        *   [Patch Changes](#patch-changes-28)
            
    *   [v6.24.1](#v6241)
        *   [Patch Changes](#patch-changes-29)
            
    *   [v6.24.0](#v6240)
        *   [What's Changed](#whats-changed-6)
            *   [Lazy Route Discovery (a.k.a. "Fog of War")](#lazy-route-discovery-aka-fog-of-war)
                
        *   [Minor Changes](#minor-changes-13)
            
        *   [Patch Changes](#patch-changes-30)
            
    *   [v6.23.1](#v6231)
        *   [Patch Changes](#patch-changes-31)
            
    *   [v6.23.0](#v6230)
        *   [What's Changed](#whats-changed-7)
            *   [Data Strategy (unstable)](#data-strategy-unstable)
                
            *   [Skip Action Error Revalidation (unstable)](#skip-action-error-revalidation-unstable)
                
        *   [Minor Changes](#minor-changes-14)
            
    *   [v6.22.3](#v6223)
        *   [Patch Changes](#patch-changes-32)
            
    *   [v6.22.2](#v6222)
        *   [Patch Changes](#patch-changes-33)
            
    *   [v6.22.1](#v6221)
        *   [Patch Changes](#patch-changes-34)
            
    *   [v6.22.0](#v6220)
        *   [What's Changed](#whats-changed-8)
            *   [Core Web Vitals Technology Report Flag](#core-web-vitals-technology-report-flag)
                
        *   [Minor Changes](#minor-changes-15)
            
        *   [Patch Changes](#patch-changes-35)
            
    *   [v6.21.3](#v6213)
        *   [Patch Changes](#patch-changes-36)
            
    *   [v6.21.2](#v6212)
        *   [Patch Changes](#patch-changes-37)
            
    *   [v6.21.1](#v6211)
        *   [Patch Changes](#patch-changes-38)
            
    *   [v6.21.0](#v6210)
        *   [What's Changed](#whats-changed-9)
            *   [`future.v7_relativeSplatPath`](#futurev7_relativesplatpath)
                
            *   [Partial Hydration](#partial-hydration)
                
        *   [Minor Changes](#minor-changes-16)
            
        *   [Patch Changes](#patch-changes-39)
            
    *   [v6.20.1](#v6201)
        *   [Patch Changes](#patch-changes-40)
            
    *   [v6.20.0](#v6200)
        *   [Minor Changes](#minor-changes-17)
            
        *   [Patch Changes](#patch-changes-41)
            
    *   [v6.19.0](#v6190)
        *   [What's Changed](#whats-changed-10)
            *   [`unstable_flushSync` API](#unstable_flushsync-api)
                
        *   [Minor Changes](#minor-changes-18)
            
        *   [Patch Changes](#patch-changes-42)
            
    *   [v6.18.0](#v6180)
        *   [What's Changed](#whats-changed-11)
            *   [New Fetcher APIs](#new-fetcher-apis)
                
            *   [Persistence Future Flag (`future.v7_fetcherPersist`)](#persistence-future-flag-futurev7_fetcherpersist)
                
        *   [Minor Changes](#minor-changes-19)
            
        *   [Patch Changes](#patch-changes-43)
            
    *   [v6.17.0](#v6170)
        *   [What's Changed](#whats-changed-12)
            *   [View Transitions 🚀](#view-transitions-)
                
        *   [Minor Changes](#minor-changes-20)
            
        *   [Patch Changes](#patch-changes-44)
            
    *   [v6.16.0](#v6160)
        *   [Minor Changes](#minor-changes-21)
            
        *   [Patch Changes](#patch-changes-45)
            
    *   [v6.15.0](#v6150)
        *   [Minor Changes](#minor-changes-22)
            
        *   [Patch Changes](#patch-changes-46)
            
    *   [v6.14.2](#v6142)
        *   [Patch Changes](#patch-changes-47)
            
    *   [v6.14.1](#v6141)
        *   [Patch Changes](#patch-changes-48)
            
    *   [v6.14.0](#v6140)
        *   [What's Changed](#whats-changed-13)
            *   [JSON/Text Submissions](#jsontext-submissions)
                
        *   [Minor Changes](#minor-changes-23)
            
        *   [Patch Changes](#patch-changes-49)
            
    *   [v6.13.0](#v6130)
        *   [What's Changed](#whats-changed-14)
            *   [`future.v7_startTransition`](#futurev7_starttransition)
                
        *   [Minor Changes](#minor-changes-24)
            
        *   [Patch Changes](#patch-changes-50)
            
    *   [v6.12.1](#v6121)
        *   [Patch Changes](#patch-changes-51)
            
    *   [v6.12.0](#v6120)
        *   [What's Changed](#whats-changed-15)
            *   [`React.startTransition` support](#reactstarttransition-support)
                
        *   [Minor Changes](#minor-changes-25)
            
        *   [Patch Changes](#patch-changes-52)
            
    *   [v6.11.2](#v6112)
        *   [Patch Changes](#patch-changes-53)
            
    *   [v6.11.1](#v6111)
        *   [Patch Changes](#patch-changes-54)
            
    *   [v6.11.0](#v6110)
        *   [Minor Changes](#minor-changes-26)
            
        *   [Patch Changes](#patch-changes-55)
            
    *   [v6.10.0](#v6100)
        *   [What's Changed](#whats-changed-16)
            
        *   [Minor Changes](#minor-changes-27)
            *   [`future.v7_normalizeFormMethod`](#futurev7_normalizeformmethod)
                
        *   [Patch Changes](#patch-changes-56)
            
    *   [v6.9.0](#v690)
        *   [What's Changed](#whats-changed-17)
            *   [`Component`/`ErrorBoundary` route properties](#componenterrorboundary-route-properties)
                
            *   [Introducing Lazy Route Modules](#introducing-lazy-route-modules)
                
        *   [Minor Changes](#minor-changes-28)
            
        *   [Patch Changes](#patch-changes-57)
            
    *   [v6.8.2](#v682)
        *   [Patch Changes](#patch-changes-58)
            
    *   [v6.8.1](#v681)
        *   [Patch Changes](#patch-changes-59)
            
    *   [v6.8.0](#v680)
        *   [Minor Changes](#minor-changes-29)
            
        *   [Patch Changes](#patch-changes-60)
            
    *   [v6.7.0](#v670)
        *   [Minor Changes](#minor-changes-30)
            
        *   [Patch Changes](#patch-changes-61)
            
    *   [v6.6.2](#v662)
        *   [Patch Changes](#patch-changes-62)
            
    *   [v6.6.1](#v661)
        *   [Patch Changes](#patch-changes-63)
            
    *   [v6.6.0](#v660)
        *   [What's Changed](#whats-changed-18)
            
        *   [Minor Changes](#minor-changes-31)
            
        *   [Patch Changes](#patch-changes-64)
            
    *   [v6.5.0](#v650)
        *   [What's Changed](#whats-changed-19)
            
        *   [Minor Changes](#minor-changes-32)
            
        *   [Patch Changes](#patch-changes-65)
            
    *   [v6.4.5](#v645)
        *   [Patch Changes](#patch-changes-66)
            
    *   [v6.4.4](#v644)
        *   [Patch Changes](#patch-changes-67)
            
    *   [v6.4.3](#v643)
        *   [Patch Changes](#patch-changes-68)
            
    *   [v6.4.2](#v642)
        *   [Patch Changes](#patch-changes-69)
            
    *   [v6.4.1](#v641)
        *   [Patch Changes](#patch-changes-70)
            
    *   [v6.4.0](#v640)
        *   [What's Changed](#whats-changed-20)
            *   [Remix Data APIs](#remix-data-apis)
                
        *   [Patch Changes](#patch-changes-71)
            
    *   [v6.3.0](#v630)
        *   [Minor Changes](#minor-changes-33)
            
    *   [v6.2.2](#v622)
        *   [Patch Changes](#patch-changes-72)
            
    *   [v6.2.1](#v621)
        *   [Patch Changes](#patch-changes-73)
            
    *   [v6.2.0](#v620)
        *   [Minor Changes](#minor-changes-34)
            
        *   [Patch Changes](#patch-changes-74)
            
    *   [v6.1.1](#v611)
        *   [Patch Changes](#patch-changes-75)
            
    *   [v6.1.0](#v610)
        *   [Minor Changes](#minor-changes-35)
            
        *   [Patch Changes](#patch-changes-76)
            
    *   [v6.0.2](#v602)
        *   [Patch Changes](#patch-changes-77)
            
    *   [v6.0.1](#v601)
        *   [Patch Changes](#patch-changes-78)
            
    *   [v6.0.0](#v600)
        

[](#v760)
v7.6.0
----------------

Date: 2025-05-08

### [](#whats-changed)
What's Changed

#### [](#routediscovery-config-option)
`routeDiscovery` Config Option

We've added a new config option in `7.6.0` which grants you more control over the Lazy Route Discovery feature. You can now configure the `/__manifest` path if you're running multiple RR applications on the same server, or you can also disable the feature entirely if your application is small enough and the feature isn't necessary.

    // react-router.config.ts
    
    export default {
      // You can modify the manifest path used:
      routeDiscovery: { mode: "lazy", manifestPath: "/custom-manifest" }
    
      // Or you can disable this feature entirely and include all routes in the
      // manifest on initial document load:
      routeDiscovery: { mode: "initial" }
    
      // If you don't specify anything, the default config is as follows, which enables
      // Lazy Route Discovery and makes manifest requests to the `/__manifest` path:
      // routeDiscovery: { mode: "lazy", manifestPath: "/__manifest" }
    } satisfies Config;
    

#### [](#automatic-types-for-future-flags)
Automatic Types for Future Flags

Some future flags alter the way types should work in React Router. Previously, you had to remember to manually opt-in to the new types. For example, for `future.unstable_middleware`:

    // react-router.config.ts
    
    // Step 1: Enable middleware
    export default {
      future: {
        unstable_middleware: true,
      },
    };
    
    // Step 2: Enable middleware types
    declare module "react-router" {
      interface Future {
        unstable_middleware: true; // 👈 Enable middleware types
      }
    }
    

It was up to you to keep the runtime future flags synced with the types for those flags. This was confusing and error-prone.

Now, React Router will automatically enable types for future flags. That means you only need to specify the runtime future flag:

    // react-router.config.ts
    
    // Step 1: Enable middleware
    export default {
      future: {
        unstable_middleware: true,
      },
    };
    
    // No step 2! That's it!
    

Behind the scenes, React Router will generate the corresponding `declare module` into `.react-router/types`. Currently this is done in `.react-router/types/+register.ts` but this is an implementation detail that may change in the future.

### [](#minor-changes)
Minor Changes

*   `react-router` - Added a new `routeDiscovery` option in `react-router.config.ts` to configure Lazy Route Discovery behavior ([#13451](https://github.com/remix-run/react-router/pull/13451)
    )
    
*   `react-router` - Add support for route component props in `createRoutesStub` ([#13528](https://github.com/remix-run/react-router/pull/13528)
    )
    
    *   This allows you to unit test your route components using the props instead of the hooks:
        
            let RoutesStub = createRoutesStub([\
              {\
                path: "/",\
                Component({ loaderData }) {\
                  let data = loaderData as { message: string };\
                  return <pre data-testid="data">Message: {data.message}</pre>;\
                },\
                loader() {\
                  return { message: "hello" };\
                },\
              },\
            ]);
            
            render(<RoutesStub />);
            
            await waitFor(() => screen.findByText("Message: hello"));
            
        
*   `@react-router/dev` - Automatic types for future flags ([#13506](https://github.com/remix-run/react-router/pull/13506)
    )
    

### [](#patch-changes)
Patch Changes

You may notice this list is a bit larger than usual! The team ate their vegetables last week and spent the week [squashing bugs](https://x.com/BrooksLybrand/status/1918406062920589731)
 to work on lowering the issue count that had ballooned a bit since the v7 release.

*   `react-router` - Fix `react-router` module augmentation for `NodeNext` ([#13498](https://github.com/remix-run/react-router/pull/13498)
    )
*   `react-router` - Don't bundle `react-router` in `react-router/dom` CJS export ([#13497](https://github.com/remix-run/react-router/pull/13497)
    )
*   `react-router` - Fix bug where a submitting `fetcher` would get stuck in a `loading` state if a revalidating `loader` redirected ([#12873](https://github.com/remix-run/react-router/pull/12873)
    )
*   `react-router` - Fix hydration error if a server `loader` returned `undefined` ([#13496](https://github.com/remix-run/react-router/pull/13496)
    )
*   `react-router` - Fix initial load 404 scenarios in data mode ([#13500](https://github.com/remix-run/react-router/pull/13500)
    )
*   `react-router` - Stabilize `useRevalidator`'s `revalidate` function ([#13542](https://github.com/remix-run/react-router/pull/13542)
    )
*   `react-router` - Preserve status code if a `clientAction` throws a `data()` result in framework mode ([#13522](https://github.com/remix-run/react-router/pull/13522)
    )
*   `react-router` - Be defensive against leading double slashes in paths to avoid `Invalid URL` errors from the URL constructor ([#13510](https://github.com/remix-run/react-router/pull/13510)
    )
    *   Note we do not sanitize/normalize these paths - we only detect them so we can avoid the error that would be thrown by `new URL("//", window.location.origin)`
*   `react-router` - Remove `Navigator` declaration for `navigator.connection.saveData` to avoid messing with any other types beyond `saveData` in user land ([#13512](https://github.com/remix-run/react-router/pull/13512)
    )
*   `react-router` - Fix `handleError` `params` values on `.data` requests for routes with a dynamic param as the last URL segment ([#13481](https://github.com/remix-run/react-router/pull/13481)
    )
*   `react-router` - Don't trigger an `ErrorBoundary` UI before the reload when we detect a manifest version mismatch in Lazy Route Discovery ([#13480](https://github.com/remix-run/react-router/pull/13480)
    )
*   `react-router` - Inline `turbo-stream@2.4.1` dependency and fix decoding ordering of `Map`/`Set` instances ([#13518](https://github.com/remix-run/react-router/pull/13518)
    )
*   `react-router` - Only render dev warnings during dev ([#13461](https://github.com/remix-run/react-router/pull/13461)
    )
*   `react-router` - Short circuit post-processing on aborted `dataStrategy` requests ([#13521](https://github.com/remix-run/react-router/pull/13521)
    )
    *   This resolves non-user-facing console errors of the form `Cannot read properties of undefined (reading 'result')`
*   `@react-router/dev` - Support project root directories without a `package.json` if it exists in a parent directory ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - When providing a custom Vite config path via the CLI `--config`/`-c` flag, default the project root directory to the directory containing the Vite config when not explicitly provided ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - In a `routes.ts` context, ensure the `--mode` flag is respected for `import.meta.env.MODE` ([#13485](https://github.com/remix-run/react-router/pull/13485)
    )
    *   Previously, `import.meta.env.MODE` within a `routes.ts` context was always `"development"` for the `dev` and `typegen --watch` commands, but otherwise resolved to `"production"`. These defaults are still in place, but if a `--mode` flag is provided, this will now take precedence.
*   `@react-router/dev` - Ensure consistent project root directory resolution logic in CLI commands ([#13472](https://github.com/remix-run/react-router/pull/13472)
    )
*   `@react-router/dev` - When executing `react-router.config.ts` and `routes.ts` with `vite-node`, ensure that PostCSS config files are ignored ([#13489](https://github.com/remix-run/react-router/pull/13489)
    )
*   `@react-router/dev` - When extracting critical CSS during development, ensure it's loaded from the client environment to avoid issues with plugins that handle the SSR environment differently ([#13503](https://github.com/remix-run/react-router/pull/13503)
    )
*   `@react-router/dev` - Fix "Status message is not supported by HTTP/2" error during dev when using HTTPS ([#13460](https://github.com/remix-run/react-router/pull/13460)
    )
*   `@react-router/dev` - Update config when `react-router.config.ts` is created or deleted during development ([#12319](https://github.com/remix-run/react-router/pull/12319)
    )
*   `@react-router/dev` - Skip unnecessary `routes.ts` evaluation before Vite build is started ([#13513](https://github.com/remix-run/react-router/pull/13513)
    )
*   `@react-router/dev` - Fix `TS2300: Duplicate identifier` errors caused by generated types ([#13499](https://github.com/remix-run/react-router/pull/13499)
    )
*   Previously, routes that had the same full path would cause duplicate entries in the generated types for `href` (`.react-router/types/+register.ts`), causing type checking errors

### [](#unstable-changes)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Fix a few bugs with error bubbling in middleware use-cases ([#13538](https://github.com/remix-run/react-router/pull/13538)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure that `build.assetsDir` in Vite config is respected when `environments.client.build.assetsDir` is not configured ([#13491](https://github.com/remix-run/react-router/pull/13491)
    )

### [](#changes-by-package)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/create-react-router/CHANGELOG.md#760)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router/CHANGELOG.md#760)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-architect/CHANGELOG.md#760)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-cloudflare/CHANGELOG.md#760)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-dev/CHANGELOG.md#760)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-express/CHANGELOG.md#760)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-fs-routes/CHANGELOG.md#760)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-node/CHANGELOG.md#760)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#760)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.6.0/packages/react-router-serve/CHANGELOG.md#760)
    

**Full Changelog**: [`v7.5.3...v7.6.0`](https://github.com/remix-run/react-router/compare/react-router@7.5.3...react-router@7.6.0)

[](#v753)
v7.5.3
----------------

Date: 2025-04-28

### [](#patch-changes-1)
Patch Changes

*   `react-router` - Fix bug where bubbled action errors would result in `loaderData` being cleared at the handling `ErrorBoundary` route ([#13476](https://github.com/remix-run/react-router/pull/13476)
    )
*   `react-router` - Handle redirects from `clientLoader.hydrate` initial load executions ([#13477](https://github.com/remix-run/react-router/pull/13477)
    )

**Full Changelog**: [`v7.5.2...v7.5.3`](https://github.com/remix-run/react-router/compare/react-router@7.5.2...react-router@7.5.3)

[](#v752)
v7.5.2
----------------

Date: 2025-04-24

### [](#security-notice)
Security Notice

Fixed 2 security vulnerabilities that could result in cache-poisoning attacks by sending specific headers intended for build-time usage for SPA Mode and Pre-rendering ([GHSA-f46r-rw29-r322](https://github.com/remix-run/react-router/security/advisories/GHSA-f46r-rw29-r322)
, [GHSA-cpj6-fhp6-mr6j](https://github.com/remix-run/react-router/security/advisories/GHSA-cpj6-fhp6-mr6j)
).

### [](#patch-changes-2)
Patch Changes

*   `react-router` - Adjust approach for Pre-rendering/SPA Mode via headers ([#13453](https://github.com/remix-run/react-router/pull/13453)
    )
*   `react-router` - Update Single Fetch to also handle the 204 redirects used in `?_data` requests in Remix v2 ([#13364](https://github.com/remix-run/react-router/pull/13364)
    )
    *   This allows applications to trigger a redirect on `.data` requests from outside the scope of React Router (i.e., an `express`/`hono` middleware) the same way they did in Remix v2 before Single Fetch was implemented
    *   This is a bit of an escape hatch - the recommended way to handle this is redirecting from a root route middleware
    *   To use this functionality, you may return from a `.data` request wih a response as follows:
        *   Set a 204 status code
        *   Set an `X-Remix-Redirect: <new-location>` header
        *   Optionally, set `X-Remix-Replace: true` or `X-Remix-Reload-Document: true` headers to replicate `replace()`/`redirectDocument()` functionality
    *   ⚠️ Please note that these responses rely on implementation details that are subject to change without a SemVer major release, and it is recommended you set up integration tests for your application to confirm this functionality is working correctly with each future React Router upgrade

**Full Changelog**: [`v7.5.1...v7.5.2`](https://github.com/remix-run/react-router/compare/react-router@7.5.1...react-router@7.5.2)

[](#v751)
v7.5.1
----------------

Date: 2025-04-17

### [](#patch-changes-3)
Patch Changes

*   `react-router` - When using the object-based `route.lazy` API, the `HydrateFallback` and `hydrateFallbackElement` properties are now skipped when lazy loading routes after hydration ([#13376](https://github.com/remix-run/react-router/pull/13376)
    )
    
    *   If you move the code for these properties into a separate file, since the hydrate properties were unused already (if the route wasn't present during hydration), you can avoid downloading them at all. For example:
        
            createBrowserRouter([\
              {\
                path: "/show/:showId",\
                lazy: {\
                  loader: async () => (await import("./show.loader.js")).loader,\
                  Component: async () =>\
                    (await import("./show.component.js")).Component,\
                  HydrateFallback: async () =>\
                    (await import("./show.hydrate-fallback.js")).HydrateFallback,\
                },\
              },\
            ]);
            
        
*   `react-router` - Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route ([#13253](https://github.com/remix-run/react-router/pull/13253)
    )
    
*   `react-router` - Properly revalidate pre-rendered paths when param values change when using `ssr:false` + `prerender` configs ([#13380](https://github.com/remix-run/react-router/pull/13380)
    )
    
*   `react-router` - Fix pre-rendering when a loader returns a redirect ([#13365](https://github.com/remix-run/react-router/pull/13365)
    )
    
*   `react-router` - Do not automatically add `null` to `staticHandler.query()` `context.loaderData` if routes do not have loaders ([#13223](https://github.com/remix-run/react-router/pull/13223)
    )
    
    *   This was a Remix v2 implementation detail inadvertently left in for React Router v7
    *   Now that we allow returning `undefined` from loaders, our prior check of `loaderData[routeId] !== undefined` was no longer sufficient and was changed to a `routeId in loaderData` check - these `null` values can cause issues for this new check
    *   ⚠️ This could be a "breaking bug fix" for you if you are doing manual SSR with `createStaticHandler()`/`<StaticRouterProvider>`, and using `context.loaderData` to control `<RouterProvider>` hydration behavior on the client

### [](#unstable-changes-1)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add better error messaging when `getLoadContext` is not updated to return a `Map` ([#13242](https://github.com/remix-run/react-router/pull/13242)
    )
*   `react-router` - Update context type for `LoaderFunctionArgs`/`ActionFunctionArgs` when middleware is enabled ([#13381](https://github.com/remix-run/react-router/pull/13381)
    )
*   `react-router` - Add a new `unstable_runClientMiddleware` argument to `dataStrategy` to enable middleware execution in custom `dataStrategy` implementations ([#13395](https://github.com/remix-run/react-router/pull/13395)
    )
*   `react-router` - Add support for the new `unstable_shouldCallHandler`/`unstable_shouldRevalidateArgs` APIs in `dataStrategy` ([#13253](https://github.com/remix-run/react-router/pull/13253)
    )

**Full Changelog**: [`v7.5.0...v7.5.1`](https://github.com/remix-run/react-router/compare/react-router@7.5.0...react-router@7.5.1)

[](#v750)
v7.5.0
----------------

Date: 2025-04-04

### [](#whats-changed-1)
What's Changed

#### [](#routelazy-object-api)
`route.lazy` Object API

We've introduced a new `route.lazy` API which gives you more granular control over the lazy loading of route properties that you could not achieve with the `route.lazy()` function signature. This is useful for Framework mode and performance-critical library mode applications.

    createBrowserRouter([\
      {\
        path: "/show/:showId",\
        lazy: {\
          loader: async () => (await import("./show.loader.js")).loader,\
          action: async () => (await import("./show.action.js")).action,\
          Component: async () => (await import("./show.component.js")).Component,\
        },\
      },\
    ]);
    

⚠️ This is a breaking change if you have adopted the `route.unstable_lazyMiddleware` API which has been removed in favor of `route.lazy.unstable_middleware`. See the `Unstable Changes` section below for more information.

### [](#minor-changes-1)
Minor Changes

*   `react-router` - Add granular object-based API for `route.lazy` to support lazy loading of individual route properties ([#13294](https://github.com/remix-run/react-router/pull/13294)
    )

### [](#patch-changes-4)
Patch Changes

*   `@react-router/dev` - Update optional `wrangler` peer dependency range to support `wrangler` v4 ([#13258](https://github.com/remix-run/react-router/pull/13258)
    )
*   `@react-router/dev` - Reinstate dependency optimization in the child compiler to fix `depsOptimizer is required in dev mode` errors when using `vite-plugin-cloudflare` and importing Node.js builtins ([#13317](https://github.com/remix-run/react-router/pull/13317)
    )

### [](#unstable-changes-2)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Introduce `future.unstable_subResourceIntegrity` flag that enables generation of an `importmap` with `integrity` for the scripts that will be loaded by the browser ([#13163](https://github.com/remix-run/react-router/pull/13163)
    )
*   `react-router` - Remove support for the `route.unstable_lazyMiddleware` property ([#13294](https://github.com/remix-run/react-router/pull/13294)
    )
    *   In order to lazily load middleware, you can use the new object-based `route.lazy.unstable_middleware` API
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure critical CSS in development works when using a custom Vite `base` has been configured ([#13305](https://github.com/remix-run/react-router/pull/13305)
    )

### [](#changes-by-package-1)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/create-react-router/CHANGELOG.md#750)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router/CHANGELOG.md#750)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-architect/CHANGELOG.md#750)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-cloudflare/CHANGELOG.md#750)
    
*   [`@react-router/dev`](http://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-dev/CHANGELOG.md#750)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-express/CHANGELOG.md#750)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-fs-routes/CHANGELOG.md#750)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-node/CHANGELOG.md#750)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#750)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.5.0/packages/react-router-serve/CHANGELOG.md#750)
    

**Full Changelog**: [`v7.4.1...v7.5.0`](https://github.com/remix-run/react-router/compare/react-router@7.4.1...react-router@7.5.0)

[](#v741)
v7.4.1
----------------

Date: 2025-03-28

### [](#security-notice-1)
Security Notice

Fixed a security vulnerability that allowed URL manipulation and potential cache pollution via the `Host` and `X-Forwarded-Host` headers due to inadequate port sanitization ([GHSA-4q56-crqp-v477/CVE-2025-31137](https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477)
).

### [](#patch-changes-5)
Patch Changes

*   `react-router` - Dedupe calls to `route.lazy` functions ([#13260](https://github.com/remix-run/react-router/pull/13260)
    )
*   `@react-router/dev` - Fix path in prerender error messages ([#13257](https://github.com/remix-run/react-router/pull/13257)
    )
*   `@react-router/dev` - Fix typegen for virtual modules when `moduleDetection` is set to `force` ([#13267](https://github.com/remix-run/react-router/pull/13267)
    )
*   `@react-router/express` - Better validation of `x-forwarded-host` header to prevent potential security issues ([#13309](https://github.com/remix-run/react-router/pull/13309)
    )

### [](#unstable-changes-3)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Fix types on `unstable_MiddlewareFunction` to avoid type errors when a middleware doesn't return a value ([#13311](https://github.com/remix-run/react-router/pull/13311)
    )
*   `react-router` - Add support for `route.unstable_lazyMiddleware` function to allow lazy loading of middleware logic ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )
    *   ⚠️ We do not recommend adoption of this API currently as we are likely going to change it prior to the stable release of middleware
    *   ⚠️ This may be a breaking change if your app is currently returning `unstable_middleware` from `route.lazy`
    *   The `route.unstable_middleware` property is no longer supported in the return value from `route.lazy`
    *   If you want to lazily load middleware, you must use `route.unstable_lazyMiddleware`
*   `@react-router/dev` - When both `future.unstable_middleware` and `future.unstable_splitRouteModules` are enabled, split `unstable_clientMiddleware` route exports into separate chunks when possible ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )
*   `@react-router/dev` - Improve performance of `future.unstable_middleware` by ensuring that route modules are only blocking during the middleware phase when the `unstable_clientMiddleware` has been defined ([#13210](https://github.com/remix-run/react-router/pull/13210)
    )

**Full Changelog**: [`v7.4.0...v7.4.1`](https://github.com/remix-run/react-router/compare/react-router@7.4.0...react-router@7.4.1)

[](#v740)
v7.4.0
----------------

Date: 2025-03-19

### [](#minor-changes-2)
Minor Changes

*   `@react-router/dev` - Generate types for `virtual:react-router/server-build` module ([#13152](https://github.com/remix-run/react-router/pull/13152)
    )

### [](#patch-changes-6)
Patch Changes

*   `react-router` - Fix root loader data on initial load redirects in SPA mode ([#13222](https://github.com/remix-run/react-router/pull/13222)
    )
*   `react-router` - Load ancestor pathless/index routes in lazy route discovery for upwards non-eager-discovery routing ([#13203](https://github.com/remix-run/react-router/pull/13203)
    )
*   `react-router` - Fix `shouldRevalidate` behavior for `clientLoader`\-only routes in `ssr:true` apps ([#13221](https://github.com/remix-run/react-router/pull/13221)
    )
*   `@react-router/dev` - Fix conflicts with other Vite plugins that use the `configureServer` and/or `configurePreviewServer` hooks ([#13184](https://github.com/remix-run/react-router/pull/13184)
    )

### [](#unstable-changes-4)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - If a middleware throws an error, ensure we only bubble the error itself via `next()` and are no longer leaking the `MiddlewareError` implementation detail ([#13180](https://github.com/remix-run/react-router/pull/13180)
    )
    *   ⚠️ This may be a breaking change if you are `catch`\-ing errors thrown by the `next()` function in your middlewares
*   `react-router` - Fix `RequestHandler` `loadContext` parameter type when middleware is enabled ([#13204](https://github.com/remix-run/react-router/pull/13204)
    )
*   `react-router` - Update `Route.unstable_MiddlewareFunction` to have a return value of `Response | undefined` instead of `Response | void` ([#13199](https://github.com/remix-run/react-router/pull/13199)
    )
*   `@react-router/dev` - When `future.unstable_splitRouteModules` is set to `"enforce"`, allow both splittable and unsplittable root route exports since it's always in a single chunk ([#13238](https://github.com/remix-run/react-router/pull/13238)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, allow plugins that override the default SSR environment (such as `@cloudflare/vite-plugin`) to be placed before or after the React Router plugin ([#13183](https://github.com/remix-run/react-router/pull/13183)
    )

### [](#changes-by-package-2)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/create-react-router/CHANGELOG.md#740)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router/CHANGELOG.md#740)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-architect/CHANGELOG.md#740)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-cloudflare/CHANGELOG.md#740)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-dev/CHANGELOG.md#740)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-express/CHANGELOG.md#740)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-fs-routes/CHANGELOG.md#740)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-node/CHANGELOG.md#740)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#740)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.4.0/packages/react-router-serve/CHANGELOG.md#740)
    

**Full Changelog**: [`v7.3.0...v7.4.0`](https://github.com/remix-run/react-router/compare/react-router@7.3.0...react-router@7.4.0)

[](#v730)
v7.3.0
----------------

Date: 2025-03-06

### [](#minor-changes-3)
Minor Changes

*   Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13061](https://github.com/remix-run/react-router/pull/13061)
    )

### [](#patch-changes-7)
Patch Changes

*   `react-router` - Detect and handle manifest-skew issues on new deploys during active sessions ([#13061](https://github.com/remix-run/react-router/pull/13061)
    )
    *   In framework mode, Lazy Route Discovery will now detect manifest version mismatches in active sessions after a new deploy
    *   On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
    *   On `fetcher` calls to undiscovered routes, this mismatch will trigger a document reload of the current path
*   `react-router` - Skip resource route flow in dev server in SPA mode ([#13113](https://github.com/remix-run/react-router/pull/13113)
    )
*   `react-router` - Fix single fetch `_root.data` requests when a `basename` is used ([#12898](https://github.com/remix-run/react-router/pull/12898)
    )
*   `react-router` - Fix types for `loaderData` and `actionData` that contained `Record`s ([#13139](https://github.com/remix-run/react-router/pull/13139)
    )
    *   ⚠️ This is a breaking change for users who have already adopted `unstable_SerializesTo` - see the note in the `Unstable Changes` section below for more information
*   `@react-router/dev` - Fix support for custom client `build.rollupOptions.output.entryFileNames` ([#13098](https://github.com/remix-run/react-router/pull/13098)
    )
*   `@react-router/dev` - Fix usage of `prerender` option when `serverBundles` option has been configured or provided by a preset, e.g. `vercelPreset` from `@vercel/react-router` ([#13082](https://github.com/remix-run/react-router/pull/13082)
    )
*   `@react-router/dev` - Fix support for custom `build.assetsDir` ([#13077](https://github.com/remix-run/react-router/pull/13077)
    )
*   `@react-router/dev` - Remove unused dependencies ([#13134](https://github.com/remix-run/react-router/pull/13134)
    )
*   `@react-router/dev` - Stub all routes except root in "SPA Mode" server builds to avoid issues when route modules or their dependencies import non-SSR-friendly modules ([#13023](https://github.com/remix-run/react-router/pull/13023)
    )
*   `@react-router/dev` - Remove unused Vite file system watcher ([#13133](https://github.com/remix-run/react-router/pull/13133)
    )
*   `@react-router/dev` - Fix support for custom SSR build input when `serverBundles` option has been configured ([#13107](https://github.com/remix-run/react-router/pull/13107)
    )
    *   ⚠️ Note that for consumers using the `future.unstable_viteEnvironmentApi` and `serverBundles` options together, hyphens are no longer supported in server bundle IDs since they also need to be valid Vite environment names.
*   `@react-router/dev` - Fix dev server when using HTTPS by stripping HTTP/2 pseudo headers from dev server requests ([#12830](https://github.com/remix-run/react-router/pull/12830)
    )
*   `@react-router/dev` - Lazy load Cloudflare platform proxy on first dev server request when using the `cloudflareDevProxy` Vite plugin to avoid creating unnecessary `workerd` processes ([#13016](https://github.com/remix-run/react-router/pull/13016)
    )
*   `@react-router/dev` - Fix duplicated entries in typegen for layout routes and their corresponding index route ([#13140](https://github.com/remix-run/react-router/pull/13140)
    )
*   `@react-router/express` - Update `express` `peerDependency` to include v5 ([https://github.com/remix-run/react-router/pull/13064](https://github.com/remix-run/react-router/pull/13064)
    ) ([#12961](https://github.com/remix-run/react-router/pull/12961)
    )

### [](#unstable-changes-5)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add `context` support to client side data routers (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941)
    )
*   `react-router` - Support middleware on routes (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941)
    )
*   `@react-router/dev` - Fix errors with `future.unstable_viteEnvironmentApi` when the `ssr` environment has been configured by another plugin to be a custom `Vite.DevEnvironment` rather than the default `Vite.RunnableDevEnvironment` ([#13008](https://github.com/remix-run/react-router/pull/13008)
    )
*   `@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled and the `ssr` environment has `optimizeDeps.noDiscovery` disabled, define `optimizeDeps.entries` and `optimizeDeps.include` ([#13007](https://github.com/remix-run/react-router/pull/13007)
    )

#### [](#client-side-context-unstable)
Client-side `context` (unstable)

Your application `clientLoader`/`clientAction` functions (or `loader`/`action` in library mode) will now receive a `context` parameter on the client. This is an instance of `unstable_RouterContextProvider` that you use with type-safe contexts (similar to `React.createContext`) and is most useful with the corresponding `unstable_clientMiddleware` API:

    import { unstable_createContext } from "react-router";
    
    type User = {
      /*...*/
    };
    
    const userContext = unstable_createContext<User>();
    
    const sessionMiddleware: Route.unstable_ClientMiddlewareFunction = async ({
      context,
    }) => {
      let user = await getUser();
      context.set(userContext, user);
    };
    
    export const unstable_clientMiddleware = [sessionMiddleware];
    
    export function clientLoader({ context }: Route.ClientLoaderArgs) {
      let user = context.get(userContext);
      let profile = await getProfile(user.id);
      return { profile };
    }
    

Similar to server-side requests, a fresh `context` will be created per navigation (or `fetcher` call). If you have initial data you'd like to populate in the context for every request, you can provide an `unstable_getContext` function at the root of your app:

*   Library mode - `createBrowserRouter(routes, { unstable_getContext })`
*   Framework mode - `<HydratedRouter unstable_getContext>`

This function should return an value of type `unstable_InitialContext` which is a `Map<unstable_RouterContext, unknown>` of context's and initial values:

    const loggerContext = unstable_createContext<(...args: unknown[]) => void>();
    
    function logger(...args: unknown[]) {
      console.log(new Date.toISOString(), ...args);
    }
    
    function unstable_getContext() {
      let map = new Map();
      map.set(loggerContext, logger);
      return map;
    }
    

#### [](#middleware-unstable)
Middleware (unstable)

Middleware is implemented behind a `future.unstable_middleware` flag. To enable, you must enable the flag and the types in your `react-router.config.ts` file:

    import type { Config } from "@react-router/dev/config";
    import type { Future } from "react-router";
    
    declare module "react-router" {
      interface Future {
        unstable_middleware: true; // 👈 Enable middleware types
      }
    }
    
    export default {
      future: {
        unstable_middleware: true, // 👈 Enable middleware
      },
    } satisfies Config;
    

⚠️ Middleware is unstable and should not be adopted in production. There is at least one known de-optimization in route module loading for `clientMiddleware` that we will be addressing this before a stable release.

⚠️ Enabling middleware contains a breaking change to the `context` parameter passed to your `loader`/`action` functions - see below for more information.

Once enabled, routes can define an array of middleware functions that will run sequentially before route handlers run. These functions accept the same parameters as `loader`/`action` plus an additional `next` parameter to run the remaining data pipeline. This allows middlewares to perform logic before and after handlers execute.

    // Framework mode
    export const unstable_middleware = [serverLogger, serverAuth]; // server
    export const unstable_clientMiddleware = [clientLogger]; // client
    
    // Library mode
    const routes = [\
      {\
        path: "/",\
        // Middlewares are client-side for library mode SPA's\
        unstable_middleware: [clientLogger, clientAuth],\
        loader: rootLoader,\
        Component: Root,\
      },\
    ];
    

Here's a simple example of a client-side logging middleware that can be placed on the root route:

    const clientLogger: Route.unstable_ClientMiddlewareFunction = async (
      { request },
      next
    ) => {
      let start = performance.now();
    
      // Run the remaining middlewares and all route loaders
      await next();
    
      let duration = performance.now() - start;
      console.log(`Navigated to ${request.url} (${duration}ms)`);
    };
    

Note that in the above example, the `next`/`middleware` functions don't return anything. This is by design as on the client there is no "response" to send over the network like there would be for middlewares running on the server. The data is all handled behind the scenes by the stateful `router`.

For a server-side middleware, the `next` function will return the HTTP `Response` that React Router will be sending across the wire, thus giving you a chance to make changes as needed. You may throw a new response to short circuit and respond immediately, or you may return a new or altered response to override the default returned by `next()`.

    const serverLogger: Route.unstable_MiddlewareFunction = async (
      { request, params, context },
      next
    ) => {
      let start = performance.now();
    
      // 👇 Grab the response here
      let res = await next();
    
      let duration = performance.now() - start;
      console.log(`Navigated to ${request.url} (${duration}ms)`);
    
      // 👇 And return it here (optional if you don't modify the response)
      return res;
    };
    

You can throw a `redirect` from a middleware to short circuit any remaining processing:

    import { sessionContext } from "../context";
    const serverAuth: Route.unstable_MiddlewareFunction = (
      { request, params, context },
      next
    ) => {
      let session = context.get(sessionContext);
      let user = session.get("user");
      if (!user) {
        session.set("returnTo", request.url);
        throw redirect("/login", 302);
      }
    };
    

_Note that in cases like this where you don't need to do any post-processing you don't need to call the `next` function or return a `Response`._

Here's another example of using a server middleware to detect 404s and check the CMS for a redirect:

    const redirects: Route.unstable_MiddlewareFunction = async ({
      request,
      next,
    }) => {
      // attempt to handle the request
      let res = await next();
    
      // if it's a 404, check the CMS for a redirect, do it last
      // because it's expensive
      if (res.status === 404) {
        let cmsRedirect = await checkCMSRedirects(request.url);
        if (cmsRedirect) {
          throw redirect(cmsRedirect, 302);
        }
      }
    
      return res;
    };
    

For more information on the `middleware` API/design, please see the [decision doc](https://github.com/remix-run/react-router/blob/release-next/decisions/0014-context-middleware.md)
.

##### [](#middleware-context-parameter)
Middleware `context` parameter

When middleware is enabled, your application will use a different type of `context` parameter in your loaders and actions to provide better type safety. Instead of `AppLoadContext`, `context` will now be an instance of `ContextProvider` that you can use with type-safe contexts (similar to `React.createContext`):

    import { unstable_createContext } from "react-router";
    import { Route } from "./+types/root";
    import type { Session } from "./sessions.server";
    import { getSession } from "./sessions.server";
    
    let sessionContext = unstable_createContext<Session>();
    
    const sessionMiddleware: Route.unstable_MiddlewareFunction = ({
      context,
      request,
    }) => {
      let session = await getSession(request);
      context.set(sessionContext, session);
      //                          ^ must be of type Session
    };
    
    // ... then in some downstream middleware
    const loggerMiddleware: Route.unstable_MiddlewareFunction = ({
      context,
      request,
    }) => {
      let session = context.get(sessionContext);
      //  ^ typeof Session
      console.log(session.get("userId"), request.method, request.url);
    };
    
    // ... or some downstream loader
    export function loader({ context }: Route.LoaderArgs) {
      let session = context.get(sessionContext);
      let profile = await getProfile(session.get("userId"));
      return { profile };
    }
    

If you are using a custom server with a `getLoadContext` function, the return value for initial context values passed from the server adapter layer is no longer an object and should now return an `unstable_InitialContext` (`Map<RouterContext, unknown>`):

    let adapterContext = unstable_createContext<MyAdapterContext>();
    
    function getLoadContext(req, res): unstable_InitialContext {
      let map = new Map();
      map.set(adapterContext, getAdapterContext(req));
      return map;
    }
    

#### [](#unstable_serializesto)
`unstable_SerializesTo`

`unstable_SerializesTo` added a way to register custom serialization types in Single Fetch for other library and framework authors like Apollo. It was implemented with branded type whose branded property that was made optional so that casting arbitrary values was easy:

    // without the brand being marked as optional
    let x1 = 42 as unknown as unstable_SerializesTo<number>;
    //          ^^^^^^^^^^
    
    // with the brand being marked as optional
    let x2 = 42 as unstable_SerializesTo<number>;
    

However, this broke type inference in `loaderData` and `actionData` for any `Record` types as those would now (incorrectly) match `unstable_SerializesTo`. This affected all users, not just those that depended on `unstable_SerializesTo`. To fix this, the branded property of `unstable_SerializesTo` is marked as required instead of optional.

For library and framework authors using `unstable_SerializesTo`, you may need to add `as unknown` casts before casting to `unstable_SerializesTo`.

### [](#changes-by-package-3)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/create-react-router/CHANGELOG.md#730)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router/CHANGELOG.md#730)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-architect/CHANGELOG.md#730)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-cloudflare/CHANGELOG.md#730)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-dev/CHANGELOG.md#730)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-express/CHANGELOG.md#730)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-fs-routes/CHANGELOG.md#730)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-node/CHANGELOG.md#730)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#730)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.3.0/packages/react-router-serve/CHANGELOG.md#730)
    

**Full Changelog**: [`v7.2.0...v7.3.0`](https://github.com/remix-run/react-router/compare/react-router@7.2.0...react-router@7.3.0)

[](#v720)
v7.2.0
----------------

Date: 2025-02-18

### [](#whats-changed-2)
What's Changed

#### [](#type-safe-href-utility)
Type-safe `href` utility

In framework mode, we now provide you with a fully type-safe `href` utility to give you all the warm and fuzzy feelings of path auto-completion and param validation for links in your application:

    import { href } from "react-router";
    
    export default function Component() {
      const link = href("/blog/:slug", { slug: "my-first-post" });
      //                ^ type-safe!     ^ Also type-safe!
    
      return (
        <main>
          <Link to={href("/products/:id", { id: "asdf" })} />
          <NavLink to={href("/:lang?/about", { lang: "en" })} />
        </main>
      );
    }
    

You'll now get type errors if you pass a bad path value or a bad param value:

    const badPath = href("/not/a/valid/path");
    //                   ^ Error!
    
    const badParam = href("/blog/:slug", { oops: "bad param" });
    //                                     ^ Error!
    

#### [](#prerendering-with-a-spa-fallback)
Prerendering with a SPA Fallback

This release enhances the ability to use a combination of pre-rendered paths alongside other paths that operate in "SPA Mode" when pre-rendering with `ssr:false`.

*   If you specify `ssr:false` without a `prerender` config, this is considered "SPA Mode" and the generated `index.html` file will only render down to the root route and will be able to hydrate for any valid application path
*   If you specify `ssr:false` with a `prerender` config but _do not_ include the `/` path (i.e., `prerender: ['/blog/post']`), then we still generate a "SPA Mode" `index.html` file that can hydrate for any path in the application
*   If you specify `ssr:false` and include the `/` path in your `prerender` config, the generated `index.html` file will be specific to the root index route, so we will now also generate a separate "SPA Mode" file in `__spa-fallback.html` that you can serve/hydrate for non-prerendered paths

For more info, see the [Pre-rendering](https://reactrouter.com/dev/how-to/pre-rendering#pre-rendering-with-a-spa-fallback)
 docs for more info.

#### [](#allow-a-root-loader-in-spa-mode)
Allow a root `loader` in SPA Mode

SPA Mode used to prohibit the use of loaders in all routes so that we could hydrate for any path in the application. However, because the root route is always rendered at build time, we can lift this restriction for the root route.

In order to use your build-time loader data during pre-rendering, we now also expose the `loaderData` as an optional prop for the `HydrateFallback` component on routes:

*   This will be defined so long as the `HydrateFallback` is rendering because _children_ routes are loading
*   This will be `undefined` if the `HydrateFallback` is rendering because the route itself has it's own hydrating `clientLoader`
    *   In SPA mode, this will allow you to render loader root data into the SPA Mode HTML file

### [](#minor-changes-4)
Minor Changes

*   `react-router` - New type-safe `href` utility that guarantees links point to actual paths in your app ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )
*   `@react-router/dev` - Generate a "SPA fallback" HTML file when pre-rendering the `/` route with `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
*   `@react-router/dev` - Allow a `loader` in the root route in SPA mode because it can be called/server-rendered at build time ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   `Route.HydrateFallbackProps` now also receives `loaderData`

### [](#patch-changes-8)
Patch Changes

*   `react-router` - Disable Lazy Route Discovery for all `ssr:false` apps and not just "SPA Mode" because there is no runtime server to serve the search-param-configured `__manifest` requests ([#12894](https://github.com/remix-run/react-router/pull/12894)
    )
    *   We previously only disabled this for "SPA Mode" but we realized it should apply to all `ssr:false` apps
    *   In those `prerender` scenarios we would pre-render the `/__manifest` file but that makes some unnecessary assumptions about the static file server behaviors
*   `react-router` - Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
*   `react-router` - Properly handle revalidations to across a pre-render/SPA boundary ([#13021](https://github.com/remix-run/react-router/pull/13021)
    )
    *   In "hybrid" applications where some routes are pre-rendered and some are served from a SPA fallback, we need to avoid making `.data` requests if the path wasn't pre-rendered because the request will 404
    *   We don't know all the pre-rendered paths client-side, however:
        *   All `loader` data in `ssr:false` mode is static because it's generated at build time
        *   A route must use a `clientLoader` to do anything dynamic
        *   Therefore, if a route only has a `loader` and not a `clientLoader`, we disable revalidation by default because there is no new data to retrieve
        *   We short circuit and skip single fetch `.data` request logic if there are no server loaders with `shouldLoad=true` in our single fetch `dataStrategy`
        *   This ensures that the route doesn't cause a `.data` request that would 404 after a submission
*   `react-router` - Align dev server behavior with static file server behavior when `ssr:false` is set ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   When no `prerender` config exists, only SSR down to the root `HydrateFallback` (SPA Mode)
    *   When a `prerender` config exists but the current path is not pre-rendered, only SSR down to the root `HydrateFallback` (SPA Fallback)
    *   Return a 404 on `.data` requests to non-pre-rendered paths
*   `react-router` - Improve prefetch performance of CSS side effects in framework mode ([#12889](https://github.com/remix-run/react-router/pull/12889)
    )
*   `react-router` - Properly handle interrupted manifest requests in lazy route discovery ([#12915](https://github.com/remix-run/react-router/pull/12915)
    )
*   `@react-router/dev` - Handle custom `envDir` in Vite config ([#12969](https://github.com/remix-run/react-router/pull/12969)
    )
*   `@react-router/dev` - Fix CLI parsing to allow argument-less `npx react-router` usage ([#12925](https://github.com/remix-run/react-router/pull/12925)
    )
*   `@react-router/dev` - Skip action-only resource routes when using `prerender:true` ([#13004](https://github.com/remix-run/react-router/pull/13004)
    )
*   `@react-router/dev` - Enhance invalid export detection when using `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948)
    )
    *   `headers`/`action` functions are prohibited in all routes with `ssr:false` because there will be no runtime server on which to run them
    *   `loader` functions are more nuanced and depend on whether a given route is prerendered
        *   When using `ssr:false` without a `prerender` config, only the `root` route can have a `loader`
        *   When using `ssr:false` with a `prerender` config, only routes matched by a `prerender` path can have a `loader`
*   `@react-router/dev` - Error at build time in `ssr:false` + `prerender` apps for the edge case scenario of: ([#13021](https://github.com/remix-run/react-router/pull/13021)
    )
    *   A parent route has only a `loader` (does not have a `clientLoader`)
    *   The parent route is pre-rendered
    *   The parent route has children routes which are not prerendered
    *   This means that when the child paths are loaded via the SPA fallback, the parent won't have any `loaderData` because there is no server on which to run the `loader`
    *   This can be resolved by either adding a parent `clientLoader` or pre-rendering the child paths
    *   If you add a `clientLoader`, calling the `serverLoader()` on non-prerendered paths will throw a 404
*   `@react-router/dev` - Limit prerendered resource route `.data` files to only the target route ([#13004](https://github.com/remix-run/react-router/pull/13004)
    )
*   `@react-router/dev` - Fix pre-rendering of binary files ([#13039](https://github.com/remix-run/react-router/pull/13039)
    )
*   `@react-router/dev` - Fix typegen for repeated params ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )
    *   In React Router, path parameters are keyed by their name, so for a path pattern like `/a/:id/b/:id?/c/:id`, the last `:id` will set the value for `id` in `useParams` and the `params` prop
        *   For example, `/a/1/b/2/c/3` will result in the value `{ id: 3 }` at runtime
    *   Previously, generated types for params incorrectly modeled repeated params with an array
        *   For example, `/a/1/b/2/c/3` generated a type like `{ id: [1,2,3] }`.
    *   To be consistent with runtime behavior, the generated types now correctly model the "last one wins" semantics of path parameters.
        *   For example, `/a/1/b/2/c/3` now generates a type like `{ id: 3 }`.
*   `@react-router/dev` - Fix path to load `package.json` for `react-router --version` ([#13012](https://github.com/remix-run/react-router/pull/13012)
    )

### [](#unstable-changes-6)
Unstable Changes

⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags)
 are not recommended for production use_

*   `react-router` - Add `unstable_SerializesTo` brand type for library authors to register types serializable by React Router's streaming format (`turbo-stream`) ([#12264](https://github.com/remix-run/react-router/pull/12264)
    )
*   `@react-router/dev` - Add unstable support for splitting route modules in framework mode via `future.unstable_splitRouteModules` ([#11871](https://github.com/remix-run/react-router/pull/11871)
    )
*   `@react-router/dev` - Add `future.unstable_viteEnvironmentApi` flag to enable experimental Vite Environment API support ([#12936](https://github.com/remix-run/react-router/pull/12936)
    )

#### [](#split-route-modules-unstable)
Split Route Modules (unstable)

> ⚠️ This feature is currently [unstable](https://reactrouter.com/community/api-development-strategy#unstable-flags)
> , enabled by the `future.unstable_splitRouteModules` flag. We’d love any interested users to play with it locally and provide feedback, but we do not recommend using it in production yet.
> 
> If you do choose to adopt this flag in production, please ensure you do sufficient testing against your production build to ensure that the optimization is working as expected.

One of the conveniences of the [Route Module API](https://reactrouter.com/start/framework/route-module)
 is that everything a route needs is in a single file. Unfortunately this comes with a performance cost in some cases when using the `clientLoader`, `clientAction`, and `HydrateFallback` APIs.

As a basic example, consider this route module:

    import { MassiveComponent } from "~/components";
    
    export async function clientLoader() {
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      return <MassiveComponent data={loaderData} />;
    }
    

In this example we have a minimal `clientLoader` export that makes a basic fetch call, whereas the default component export is much larger. This is a problem for performance because it means that if we want to navigate to this route client-side, the entire route module must be downloaded before the client loader can start running.

To visualize this as a timeline:

In the following timeline diagrams, different characters are used within the Route Module bars to denote the different Route Module APIs being exported.

    Get Route Module:  |--=======|
    Run clientLoader:            |-----|
    Render:                            |-|
    

Instead, we want to optimize this to the following:

    Get clientLoader:  |--|
    Get Component:     |=======|
    Run clientLoader:     |-----|
    Render:                     |-|
    

To achieve this optimization, React Router will split the route module into multiple smaller modules during the production build process. In this case, we'll end up with two separate [virtual modules](https://vite.dev/guide/api-plugin#virtual-modules-convention)
 — one for the client loader and one for the component and its dependencies.

    export async function clientLoader() {
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    

    import { MassiveComponent } from "~/components";
    
    export default function Component({ loaderData }) {
      return <MassiveComponent data={loaderData} />;
    }
    

> 💡 This optimization is automatically applied in framework mode, but you can also implement it in library mode via `route.lazy` and authoring your route in multiple files as covered in our blog post on [lazy loading route modules.](https://remix.run/blog/lazy-loading-routes#advanced-usage-and-optimizations)

Now that these are available as separate modules, the client loader and the component can be downloaded in parallel. This means that the client loader can be executed as soon as it's ready without having to wait for the component.

This optimization is even more pronounced when more Route Module APIs are used. For example, when using `clientLoader`, `clientAction` and `HydrateFallback`, the timeline for a single route module during a client-side navigation might look like this:

    Get Route Module:     |--~~++++=======|
    Run clientLoader:                     |-----|
    Render:                                     |-|
    

This would instead be optimized to the following:

    Get clientLoader:     |--|
    Get clientAction:     |~~|
    Get HydrateFallback:  SKIPPED
    Get Component:        |=======|
    Run clientLoader:        |-----|
    Render:                        |-|
    

Note that this optimization only works when the Route Module APIs being split don't share code within the same file. For example, the following route module can't be split:

    import { MassiveComponent } from "~/components";
    
    const shared = () => console.log("hello");
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

This route will still work, but since both the client loader and the component depend on the `shared` function defined within the same file, it will be de-optimized into a single route module.

To avoid this, you can extract any code shared between exports into a separate file. For example:

    export const shared = () => console.log("hello");
    

You can then import this shared code in your route module without triggering the de-optimization:

    import { MassiveComponent } from "~/components";
    import { shared } from "./shared";
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

Since the shared code is in its own module, React Router is now able to split this route module into two separate virtual modules:

    import { shared } from "./shared";
    
    export async function clientLoader() {
      shared();
      return await fetch("https://example.com/api").then((response) =>
        response.json()
      );
    }
    

    import { MassiveComponent } from "~/components";
    import { shared } from "./shared";
    
    export default function Component({ loaderData }) {
      shared();
      return <MassiveComponent data={loaderData} />;
    }
    

If your project is particularly performance sensitive, you can set the `unstable_splitRouteModules` future flag to `"enforce"`:

    export default {
      future: {
        unstable_splitRouteModules: "enforce",
      },
    };
    

This setting will raise an error if any route modules can't be split:

    Error splitting route module: routes/example/route.tsx
    
    - clientLoader
    
    This export could not be split into its own chunk because it shares code with other exports. You should extract any shared code into its own module and then import it within the route module.
    

### [](#changes-by-package-4)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/create-react-router/CHANGELOG.md#720)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router/CHANGELOG.md#720)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-architect/CHANGELOG.md#720)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-cloudflare/CHANGELOG.md#720)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-dev/CHANGELOG.md#720)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-express/CHANGELOG.md#720)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-fs-routes/CHANGELOG.md#720)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-node/CHANGELOG.md#720)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#720)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.2.0/packages/react-router-serve/CHANGELOG.md#720)
    

**Full Changelog**: [`v7.1.5...v7.2.0`](https://github.com/remix-run/react-router/compare/react-router@7.1.5...react-router@7.2.0)

[](#v715)
v7.1.5
----------------

Date: 2025-01-31

### [](#patch-changes-9)
Patch Changes

*   `react-router` - Fix regression introduced in `7.1.4` via [#12800](https://github.com/remix-run/react-router/pull/12800)
     that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#12927](https://github.com/remix-run/react-router/pull/12927)
    )

**Full Changelog**: [`v7.1.4...v7.1.5`](https://github.com/remix-run/react-router/compare/react-router@7.1.4...react-router@7.1.5)

[](#v714)
v7.1.4
----------------

Date: 2025-01-30

### [](#patch-changes-10)
Patch Changes

*   `@react-router/dev` - Properly resolve Windows file paths to scan for Vite's dependency optimization when using the `unstable_optimizeDeps` future flag ([#12637](https://github.com/remix-run/react-router/pull/12637)
    )
*   `@react-router/dev` - Fix prerendering when using a custom server - previously we ended up trying to import the users custom server when we actually want to import the virtual server build module ([#12759](https://github.com/remix-run/react-router/pull/12759)
    )
*   `react-router` - Properly handle status codes that cannot have a body in single fetch responses (204, etc.) ([#12760](https://github.com/remix-run/react-router/pull/12760)
    )
*   `react-router` - Properly bubble headers as `errorHeaders` when throwing a `data()` result ([#12846](https://github.com/remix-run/react-router/pull/12846)
    )
    *   Avoid duplication of `Set-Cookie` headers if also returned from `headers`
*   `react-router` - Stop erroring on resource routes that return raw strings/objects and instead serialize them as `text/plain` or `application/json` responses ([#12848](https://github.com/remix-run/react-router/pull/12848)
    )
    *   This only applies when accessed as a resource route without the `.data` extension
    *   When accessed from a Single Fetch `.data` request, they will still be encoded via `turbo-stream`
*   `react-router` - Optimize Lazy Route Discovery path discovery to favor a single `querySelectorAll` call at the `body` level instead of many calls at the sub-tree level ([#12731](https://github.com/remix-run/react-router/pull/12731)
    )
*   `react-router` - Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12800](https://github.com/remix-run/react-router/pull/12800)
    , [#12882](https://github.com/remix-run/react-router/pull/12882)
    )
*   `react-router` - Internal reorg to clean up some duplicated route module types ([#12799](https://github.com/remix-run/react-router/pull/12799)
    )

**Full Changelog**: [`v7.1.3...v7.1.4`](https://github.com/remix-run/react-router/compare/react-router@7.1.3...react-router@7.1.4)

[](#v713)
v7.1.3
----------------

Date: 2025-01-17

### [](#patch-changes-11)
Patch Changes

*   `@react-router/dev` - Fix `reveal` and `routes` CLI commands ([#12745](https://github.com/remix-run/react-router/pull/12745)
    )

**Full Changelog**: [`v7.1.2...v7.1.3`](https://github.com/remix-run/react-router/compare/react-router@7.1.2...react-router@7.1.3)

[](#v712)
v7.1.2
----------------

Date: 2025-01-16

### [](#patch-changes-12)
Patch Changes

*   `react-router` - Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12681](https://github.com/remix-run/react-router/pull/12681)
    )
*   `react-router` - Do not rely on `symbol` for filtering out `redirect` responses from loader data ([#12694](https://github.com/remix-run/react-router/pull/12694)
    )
    *   Previously, some projects were getting type checking errors like:
        
            error TS4058: Return type of exported function has or is using name 'redirectSymbol' from external module "node_modules/..." but cannot be named.
            
        
    *   Now that `symbol`s are not used for the `redirect` response type, these errors should no longer be present
*   `@react-router/dev` - Fix default external conditions in Vite v6 ([#12644](https://github.com/remix-run/react-router/pull/12644)
    )
    *   This fixes resolution issues with certain npm packages
*   `@react-router/dev` - Fix mismatch in prerendering html/data files when path is missing a leading slash ([#12684](https://github.com/remix-run/react-router/pull/12684)
    )
*   `@react-router/dev` - Use `module-sync` server condition when enabled in the runtime. This fixes React context mismatches (e.g. `useHref() may be used only in the context of a <Router> component.`) during development on Node 22.10.0+ when using libraries that have a peer dependency on React Router ([#12729](https://github.com/remix-run/react-router/pull/12729)
    )
*   `@react-router/dev` - Fix `react-refresh` source maps ([#12686](https://github.com/remix-run/react-router/pull/12686)
    )

**Full Changelog**: [`v7.1.1...v7.1.2`](https://github.com/remix-run/react-router/compare/react-router@7.1.1...react-router@7.1.2)

[](#v711)
v7.1.1
----------------

Date: 2024-12-23

### [](#patch-changes-13)
Patch Changes

*   `@react-router/dev` - Fix for a crash when optional args are passed to the CLI ([#12609](https://github.com/remix-run/react-router/pull/12609)
    )

**Full Changelog**: [`v7.1.0...v7.1.1`](https://github.com/remix-run/react-router/compare/react-router@7.1.0...react-router@7.1.1)

[](#v710)
v7.1.0
----------------

Date: 2024-12-20

### [](#minor-changes-5)
Minor Changes

*   Add support for Vite v6 ([#12469](https://github.com/remix-run/react-router/pull/12469)
    )

### [](#patch-changes-14)
Patch Changes

*   `react-router` - Throw unwrapped Single Fetch `redirect` to align with pre-Single Fetch behavior ([#12506](https://github.com/remix-run/react-router/pull/12506)
    )
*   `react-router` - Ignore redirects when inferring loader data types ([#12527](https://github.com/remix-run/react-router/pull/12527)
    )
*   `react-router` - Remove `<Link prefetch>` warning which suffers from false positives in a lazy route discovery world ([#12485](https://github.com/remix-run/react-router/pull/12485)
    )
*   `create-react-router` - Fix missing `fs-extra` dependency ([#12556](https://github.com/remix-run/react-router/pull/12556)
    )
*   `@react-router/dev`/`@react-router/serve` - Properly initialize `NODE_ENV` if not already set for compatibility with React 19 ([#12578](https://github.com/remix-run/react-router/pull/12578)
    )
*   `@react-router/dev` - Remove the leftover/unused `abortDelay` prop from `ServerRouter` and update the default `entry.server.tsx` to use the new `streamTimeout` value for Single Fetch ([#12478](https://github.com/remix-run/react-router/pull/12478)
    )
    *   The `abortDelay` functionality was removed in v7 as it was coupled to the `defer` implementation from Remix v2, but this removal of this prop was missed
    *   If you were still using this prop in your `entry.server` file, it's likely your app is not aborting streams as you would expect and you will need to adopt the new [`streamTimeout`](https://reactrouter.com/explanation/special-files#streamtimeout)
         value introduced with Single Fetch
*   `@react-router/fs-routes` - Throw error in `flatRoutes` if routes directory is missing ([#12407](https://github.com/remix-run/react-router/pull/12407)
    )

### [](#changes-by-package-5)
Changes by Package

*   [`create-react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/create-react-router/CHANGELOG.md#710)
    
*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router/CHANGELOG.md#710)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-architect/CHANGELOG.md#710)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-cloudflare/CHANGELOG.md#710)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-dev/CHANGELOG.md#710)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-express/CHANGELOG.md#710)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-fs-routes/CHANGELOG.md#710)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-node/CHANGELOG.md#710)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#710)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.1.0/packages/react-router-serve/CHANGELOG.md#710)
    

**Full Changelog**: [`v7.0.2...v7.1.0`](https://github.com/remix-run/react-router/compare/react-router@7.0.2...react-router@7.1.0)

[](#v702)
v7.0.2
----------------

Date: 2024-12-02

### [](#patch-changes-15)
Patch Changes

*   `react-router` - Temporarily only use one build in export map so packages can have a peer dependency on react router ([#12437](https://github.com/remix-run/react-router/pull/12437)
    )
*   `@react-router/dev` - Support `moduleResolution` `Node16` and `NodeNext` ([#12440](https://github.com/remix-run/react-router/pull/12440)
    )
*   `@react-router/dev` - Generate wide `matches` and `params` types for child routes ([#12397](https://github.com/remix-run/react-router/pull/12397)
    )
    *   At runtime, `matches` includes child route matches and `params` include child route path parameters
    *   But previously, we only generated types for parent routes and the current route in `matches` and `params`
    *   To align our generated types more closely to the runtime behavior, we now generate more permissive, wider types when accessing child route information

**Full Changelog**: [`v7.0.1...v7.0.2`](https://github.com/remix-run/react-router/compare/react-router@7.0.1...react-router@7.0.2)

[](#v701)
v7.0.1
----------------

Date: 2024-11-22

### [](#patch-changes-16)
Patch Changes

*   `@react-router/dev` - Ensure typegen file watcher is cleaned up when Vite dev server restarts ([#12331](https://github.com/remix-run/react-router/pull/12331)
    )
*   `@react-router/dev` - Pass route `error` to `ErrorBoundary` as a prop ([#12338](https://github.com/remix-run/react-router/pull/12338)
    )

**Full Changelog**: [`v7.0.0...v7.0.1`](https://github.com/remix-run/react-router/compare/react-router@7.0.0...react-router@7.0.1)

[](#v700)
v7.0.0
----------------

Date: 2024-11-21

### [](#breaking-changes)
Breaking Changes

#### [](#package-restructuring)
Package Restructuring

*   The `react-router-dom`, `@remix-run/react`, `@remix-run/server-runtime`, and `@remix-run/router` have been collapsed into the `react-router` package
    *   To ease migration, `react-router-dom` is still published in v7 as a re-export of everything from `react-router`
*   The `@remix-run/cloudflare-pages` and `@remix-run/cloudflare-workers` have been collapsed into `@react-router/cloudflare` package\`
*   The `react-router-dom-v5-compat` and `react-router-native` packages are removed starting with v7

#### [](#removed-adapter-re-exports)
Removed Adapter Re-exports

Remix v2 used to re-export all common `@remix-run/server-runtime` APIs through the various runtime packages (`node`, `cloudflare`, `deno`) so that you wouldn't need an additional `@remix-run/server-runtime` dependency in your `package.json`. With the collapsing of packages into `react-router`, these common APIs are now no longer re-exported through the runtime adapters. You should import all common APIs from `react-router`, and only import runtime-specific APIs from the runtime packages:

    // Runtime-specific APIs
    import { createFileSessionStorage } from "@react-router/node";
    // Runtime-agnostic APIs
    import { redirect, useLoaderData } from "react-router";
    

#### [](#removed-apis)
Removed APIs

The following APIs have been removed in React Router v7:

*   `json`
*   `defer`
*   `unstable_composeUploadHandlers`
*   `unstable_createMemoryUploadHandler`
*   `unstable_parseMultipartFormData`

#### [](#minimum-versions)
Minimum Versions

React Router v7 requires the following minimum versions:

*   `node@20`
    *   React Router no longer provides an `installGlobals` method to [polyfill](https://reactrouter.com/dev/guides/deploying/custom-node#polyfilling-fetch)
         the `fetch` API
*   `react@18`, `react-dom@18`

#### [](#adopted-future-flag-behaviors)
Adopted Future Flag Behaviors

Remix and React Router follow an [API Development Strategy](https://reactrouter.com/en/main/guides/api-development-strategy)
 leveraging "Future Flags" to avoid introducing a slew of breaking changes in a major release. Instead, breaking changes are introduced in minor releases behind a flag, allowing users to opt-in at their convenience. In the next major release, all future flag behaviors become the default behavior.

The following previously flagged behaviors are now the default in React Router v7:

*   [React Router v6 flags](https://reactrouter.com/en/v6/upgrading/future)
    *   `future.v7_relativeSplatPath`
    *   `future.v7_startTransition`
    *   `future.v7_fetcherPersist`
    *   `future.v7_normalizeFormMethod`
    *   `future.v7_partialHydration`
    *   `future.v7_skipActionStatusRevalidation`
*   [Remix v2 flags](https://remix.run/docs/en/v2/start/future-flags)
    *   `future.v3_fetcherPersist`
    *   `future.v3_relativeSplatPath`
    *   `future.v3_throwAbortReason`
    *   `future.v3_singleFetch`
    *   `future.v3_lazyRouteDiscovery`
    *   `future.v3_optimizeDeps`

#### [](#vite-compiler)
Vite Compiler

The [Remix Vite plugin](https://remix.run/docs/en/2.12.1/start/future-flags#vite-plugin)
 is the proper way to build full-stack SSR apps using React Router v7. The former `esbuild`\-based compiler is no longer available.

**Renamed `vitePlugin` and `cloudflareDevProxyVitePlugin`**

For Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved ([#11904](https://github.com/remix-run/react-router/pull/11904)
)

    -import {
    -  vitePlugin as remix,
    -  cloudflareDevProxyVitePlugin,
    -} from "@remix/dev";
    
    +import { reactRouter } from "@react-router/dev/vite";
    +import { cloudflareDevProxy } from "@react-router/dev/vite/cloudflare";
    

**Removed `manifest` option**

For Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed. The `manifest` option been superseded by the more powerful `buildEnd` hook since it's passed the `buildManifest` argument. You can still write the build manifest to disk if needed, but you'll most likely find it more convenient to write any logic depending on the build manifest within the `buildEnd` hook itself. ([#11573](https://github.com/remix-run/react-router/pull/11573)
)

If you were using the `manifest` option, you can replace it with a `buildEnd` hook that writes the manifest to disk like this:

    // react-router.config.ts
    import { type Config } from "@react-router/dev/config";
    import { writeFile } from "node:fs/promises";
    
    export default {
      async buildEnd({ buildManifest }) {
        await writeFile(
          "build/manifest.json",
          JSON.stringify(buildManifest, null, 2),
          "utf-8"
        );
      },
    } satisfies Config;
    

#### [](#exposed-router-promises)
Exposed Router Promises

Because React 19 will have first-class support for handling promises in the render pass (via `React.use` and `useAction`), we are now comfortable exposing the promises for the APIs that previously returned `undefined`:

*   `useNavigate()`
*   `useSubmit()`
*   `useFetcher().load`
*   `useFetcher().submit`
*   `useRevalidator().revalidate()`

### [](#other-notable-changes)
Other Notable Changes

#### [](#routests)
`routes.ts`

When using the React Router Vite plugin, routes are defined in `app/routes.ts`. Route config is exported via the `routes` export, conforming to the `RouteConfig` type. Route helper functions `route`, `index`, and `layout` are provided to make declarative type-safe route definitions easier.

    // app/routes.ts
    import {
      type RouteConfig,
      route,
      index,
      layout,
    } from "@react-router/dev/routes";
    
    export const routes: RouteConfig = [\
      index("./home.tsx"),\
      route("about", "./about.tsx"),\
    \
      layout("./auth/layout.tsx", [\
        route("login", "./auth/login.tsx"),\
        route("register", "./auth/register.tsx"),\
      ]),\
    \
      route("concerts", [\
        index("./concerts/home.tsx"),\
        route(":city", "./concerts/city.tsx"),\
        route("trending", "./concerts/trending.tsx"),\
      ]),\
    ];
    

For Remix consumers migrating to React Router, you can still configure file system routing within `routes.ts` using the `@react-router/fs-routes` package. A minimal route config that reproduces the default Remix setup looks like this:

    // app/routes.ts
    import { type RouteConfig } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export const routes: RouteConfig = flatRoutes();
    

If you want to migrate from file system routing to config-based routes, you can mix and match approaches by spreading the results of the async `flatRoutes` function into the array of config-based routes.

    // app/routes.ts
    import { type RouteConfig, route } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export const routes: RouteConfig = [\
      // Example config-based route:\
      route("/hello", "./routes/hello.tsx"),\
    \
      // File system routes scoped to a different directory:\
      ...(await flatRoutes({\
        rootDirectory: "fs-routes",\
      })),\
    ];
    

If you were using Remix's `routes` option to use alternative file system routing conventions, you can adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter`.

For example, if you were using [Remix v1 route conventions](https://remix.run/docs/en/1.19.3/file-conventions/routes-files)
 in Remix v2, you can combine `@react-router/remix-config-routes-adapter` with `@remix-run/v1-route-convention` to adapt this to React Router:

    // app/routes.ts
    import { type RouteConfig } from "@react-router/dev/routes";
    import { remixConfigRoutes } from "@react-router/remix-config-routes-adapter";
    import { createRoutesFromFolders } from "@remix-run/v1-route-convention";
    
    export const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {
      return createRoutesFromFolders(defineRoutes, {
        ignoredFilePatterns: ["**/.*", "**/*.css"],
      });
    });
    

Also note that, if you were using Remix's `routes` option to define config-based routes, you can also adapt these to the new `RouteConfig` format using `@react-router/remix-config-routes-adapter` with minimal code changes. While this makes for a fast migration path, we recommend migrating any config-based routes from Remix to the new `RouteConfig` format since it's a fairly straightforward migration.

    // app/routes.ts
    -import { type RouteConfig } from "@react-router/dev/routes";
    +import { type RouteConfig, route } from "@react-router/dev/routes";
    -import { remixConfigRoutes } from "@react-router/remix-config-routes-adapter";
    
    -export const routes: RouteConfig = remixConfigRoutes(async (defineRoutes) => {
    -  defineRoutes((route) => {
    -    route("/parent", "./routes/parent.tsx", () => [\
    -      route("/child", "./routes/child.tsx"),\
    -    ]);
    -  });
    -});
    +export const routes: RouteConfig = [\
    +  route("/parent", "./routes/parent.tsx", [\
    +    route("/child", "./routes/child.tsx"),\
    +  ]),\
    +];
    

#### [](#typesafety-improvements)
Typesafety improvements

React Router now generates types for each of your route modules and passes typed props to route module component exports ([#11961](https://github.com/remix-run/react-router/pull/11961)
, [#12019](https://github.com/remix-run/react-router/pull/12019)
). You can access those types by importing them from `./+types/<route filename without extension>`.

See [_How To > Route Module Type Safety_](https://reactrouter.com/dev/how-to/route-module-type-safety)
 and [_Explanations > Type Safety_](https://reactrouter.com/dev/explanation/type-safety)
 for more details.

#### [](#prerendering)
Prerendering

React Router v7 includes a new `prerender` config in the vite plugin to support SSG use-cases. This will pre-render your `.html` and `.data` files at build time and so you can serve them statically at runtime from a running server or a CDN ([#11539](https://github.com/remix-run/react-router/pull/11539)
)

    export default defineConfig({
      plugins: [\
        reactRouter({\
          async prerender({ getStaticPaths }) {\
            let slugs = await fakeGetSlugsFromCms();\
            return [\
              ...getStaticPaths(),\
              ...slugs.map((slug) => `/product/${slug}`),\
            ];\
          },\
        }),\
        tsconfigPaths(),\
      ],
    });
    
    async function fakeGetSlugsFromCms() {
      await new Promise((r) => setTimeout(r, 1000));
      return ["shirt", "hat"];
    }
    

### [](#major-changes-react-router)
Major Changes (`react-router`)

*   Remove the original `defer` implementation in favor of using raw promises via single fetch and `turbo-stream` ([#11744](https://github.com/remix-run/react-router/pull/11744)
    )
    *   This removes these exports from React Router:
        *   `defer`
        *   `AbortedDeferredError`
        *   `type TypedDeferredData`
        *   `UNSAFE_DeferredData`
        *   `UNSAFE_DEFERRED_SYMBOL`
*   Collapse packages into `react-router`([#11505](https://github.com/remix-run/react-router/pull/11505)
    )
    *   `@remix-run/router`
    *   `react-router-dom`
    *   `@remix-run/server-runtime`
    *   `@remix-run/testing`
    *   As a note, the `react-router-dom` package is maintained to ease adoption but it simply re-exports all APIs from `react-router`
*   Drop support for Node 16, React Router SSR now requires Node 18 or higher ([#11391](https://github.com/remix-run/react-router/pull/11391)
    , [#11690](https://github.com/remix-run/react-router/pull/11690)
    )
*   Remove `future.v7_startTransition` flag ([#11696](https://github.com/remix-run/react-router/pull/11696)
    )
*   Expose the underlying router promises from the following APIs for composition in React 19 APIs: ([#11521](https://github.com/remix-run/react-router/pull/11521)
    )
*   Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697)
    )
*   Imports/Exports cleanup ([#11840](https://github.com/remix-run/react-router/pull/11840)
    )
    *   Removed the following exports that were previously public API from `@remix-run/router`
        *   types
            *   `AgnosticDataIndexRouteObject`
            *   `AgnosticDataNonIndexRouteObject`
            *   `AgnosticDataRouteMatch`
            *   `AgnosticDataRouteObject`
            *   `AgnosticIndexRouteObject`
            *   `AgnosticNonIndexRouteObject`
            *   `AgnosticRouteMatch`
            *   `AgnosticRouteObject`
            *   `TrackedPromise`
            *   `unstable_AgnosticPatchRoutesOnMissFunction`
            *   `Action` -> exported as `NavigationType` via `react-router`
            *   `Router` exported as `RemixRouter` to differentiate from RR's `<Router>`
        *   API
            *   `getToPathname` (`@private`)
            *   `joinPaths` (`@private`)
            *   `normalizePathname` (`@private`)
            *   `resolveTo` (`@private`)
            *   `stripBasename` (`@private`)
            *   `createBrowserHistory` -> in favor of `createBrowserRouter`
            *   `createHashHistory` -> in favor of `createHashRouter`
            *   `createMemoryHistory` -> in favor of `createMemoryRouter`
            *   `createRouter`
            *   `createStaticHandler` -> in favor of wrapper `createStaticHandler` in RR Dom
            *   `getStaticContextFromError`
    *   Removed the following exports that were previously public API from `react-router`
        *   `Hash`
        *   `Pathname`
        *   `Search`
*   Remove `future.v7_prependBasename` from the internalized `@remix-run/router` package ([#11726](https://github.com/remix-run/react-router/pull/11726)
    )
*   Remove `future.v7_throwAbortReason` from internalized `@remix-run/router` package ([#11728](https://github.com/remix-run/react-router/pull/11728)
    )
*   Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675)
    )
*   Renamed `RemixContext` to `FrameworkContext` ([#11705](https://github.com/remix-run/react-router/pull/11705)
    )
*   Update the minimum React version to 18 ([#11689](https://github.com/remix-run/react-router/pull/11689)
    )
*   `PrefetchPageDescriptor` replaced by `PageLinkDescriptor` ([#11960](https://github.com/remix-run/react-router/pull/11960)
    )
*   Remove the `future.v7_partialHydration` flag ([#11725](https://github.com/remix-run/react-router/pull/11725)
    )
    *   This also removes the `<RouterProvider fallbackElement>` prop
        *   To migrate, move the `fallbackElement` to a `hydrateFallbackElement`/`HydrateFallback` on your root route
    *   Also worth nothing there is a related breaking changer with this future flag:
        *   Without `future.v7_partialHydration` (when using `fallbackElement`), `state.navigation` was populated during the initial load
        *   With `future.v7_partialHydration`, `state.navigation` remains in an `"idle"` state during the initial load
*   Remove `future.v7_relativeSplatPath` future flag ([#11695](https://github.com/remix-run/react-router/pull/11695)
    )
*   Remove remaining future flags ([#11820](https://github.com/remix-run/react-router/pull/11820)
    )
    *   React Router `v7_skipActionErrorRevalidation`
    *   Remix `v3_fetcherPersist`, `v3_relativeSplatPath`, `v3_throwAbortReason`
*   Rename `createRemixStub` to `createRoutesStub` ([#11692](https://github.com/remix-run/react-router/pull/11692)
    )
*   Remove `@remix-run/router` deprecated `detectErrorBoundary` option in favor of `mapRouteProperties` ([#11751](https://github.com/remix-run/react-router/pull/11751)
    )
*   Add `react-router/dom` subpath export to properly enable `react-dom` as an optional `peerDependency` ([#11851](https://github.com/remix-run/react-router/pull/11851)
    )
    *   This ensures that we don't blindly `import ReactDOM from "react-dom"` in `<RouterProvider>` in order to access `ReactDOM.flushSync()`, since that would break `createMemoryRouter` use cases in non-DOM environments
    *   DOM environments should import from `react-router/dom` to get the proper component that makes `ReactDOM.flushSync()` available:
        *   If you are using the Vite plugin, use this in your `entry.client.tsx`:
            *   `import { HydratedRouter } from 'react-router/dom'`
        *   If you are not using the Vite plugin and are manually calling `createBrowserRouter`/`createHashRouter`:
            *   `import { RouterProvider } from "react-router/dom"`
*   Remove `future.v7_fetcherPersist` flag ([#11731](https://github.com/remix-run/react-router/pull/11731)
    )
*   Allow returning `undefined` from loaders and actions ([#11680](https://github.com/remix-run/react-router/pull/11680)
    , [#12057](%5Bhttps://github.com/remix-run/react-router/pull/1205)
    )
*   Use `createRemixRouter`/`RouterProvider` in `entry.client` instead of `RemixBrowser` ([#11469](https://github.com/remix-run/react-router/pull/11469)
    )
*   Remove the deprecated `json` utility ([#12146](https://github.com/remix-run/react-router/pull/12146)
    )
    *   You can use [`Response.json`](https://developer.mozilla.org/en-US/docs/Web/API/Response/json_static)
         if you still need to construct JSON responses in your app

### [](#major-changes-react-router-1)
Major Changes (`@react-router/*`)

*   Remove `future.v3_singleFetch` flag ([#11522](https://github.com/remix-run/react-router/pull/11522)
    )
*   Drop support for Node 16 and 18, update minimum Node version to 20 ([#11690](https://github.com/remix-run/react-router/pull/11690)
    , [#12171](https://github.com/remix-run/react-router/pull/12171)
    )
    *   Remove `installGlobals()` as this should no longer be necessary
*   Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675)
    )
*   No longer re-export APIs from `react-router` through different runtime/adapter packages ([#11702](https://github.com/remix-run/react-router/pull/11702)
    )
*   For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API)
     is now required when using cookie and session APIs
    *   This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837)
        )
        *   `createCookie`
        *   `createCookieSessionStorage`
        *   `createMemorySessionStorage`
        *   `createSessionStorage`
    *   For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation](https://nodejs.org/api/webcrypto.html)
        
    *   Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
        *   `createCookieFactory`
        *   `createSessionStorageFactory`
        *   `createCookieSessionStorageFactory`
        *   `createMemorySessionStorageFactory`
*   Consolidate types previously duplicated across `@remix-run/router`, `@remix-run/server-runtime`, and `@remix-run/react` now that they all live in `react-router` ([#12177](https://github.com/remix-run/react-router/pull/12177)
    )
    *   Examples: `LoaderFunction`, `LoaderFunctionArgs`, `ActionFunction`, `ActionFunctionArgs`, `DataFunctionArgs`, `RouteManifest`, `LinksFunction`, `Route`, `EntryRoute`
    *   The `RouteManifest` type used by the "remix" code is now slightly stricter because it is using the former `@remix-run/router` `RouteManifest`
        *   `Record<string, Route> -> Record<string, Route | undefined>`
    *   Removed `AppData` type in favor of inlining `unknown` in the few locations it was used
    *   Removed `ServerRuntimeMeta*` types in favor of the `Meta*` types they were duplicated from
*   Migrate Remix v2 type generics to React Router ([#12180](https://github.com/remix-run/react-router/pull/12180)
    )
    *   These generics are provided for Remix v2 migration purposes
    *   These generics and the APIs they exist on should be considered informally deprecated in favor of the new `Route.*` types
    *   Anyone migrating from React Router v6 should probably not leverage these new generics and should migrate straight to the `Route.*` types
    *   For React Router v6 users, these generics are new and should not impact your app, with one exception
        *   `useFetcher` previously had an optional generic (used primarily by Remix v2) that expected the data type
        *   This has been updated in v7 to expect the type of the function that generates the data (i.e., `typeof loader`/`typeof action`)
        *   Therefore, you should update your usages:
            *   ❌ `useFetcher<LoaderData>()`
            *   ✅ `useFetcher<typeof loader>()`
*   Update `cookie` dependency to `^1.0.1` - please see the [release notes](https://github.com/jshttp/cookie/releases)
     for any breaking changes ([#12172](https://github.com/remix-run/react-router/pull/12172)
    )
*   `@react-router/cloudflare` - For Remix consumers migrating to React Router, all exports from `@remix-run/cloudflare-pages` are now provided for React Router consumers in the `@react-router/cloudflare` package. There is no longer a separate package for Cloudflare Pages. ([#11801](https://github.com/remix-run/react-router/pull/11801)
    )
*   `@react-router/cloudflare` - The `@remix-run/cloudflare-workers` package has been deprecated. Remix consumers migrating to React Router should use the `@react-router/cloudflare` package directly. For guidance on how to use `@react-router/cloudflare` within a Cloudflare Workers context, refer to the Cloudflare Workers template. ([#11801](https://github.com/remix-run/react-router/pull/11801)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router, the `vitePlugin` and `cloudflareDevProxyVitePlugin` exports have been renamed and moved. ([#11904](https://github.com/remix-run/react-router/pull/11904)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router who used the Vite plugin's `buildEnd` hook, the resolved `reactRouterConfig` object no longer contains a `publicPath` property since this belongs to Vite, not React Router ([#11575](https://github.com/remix-run/react-router/pull/11575)
    )
*   `@react-router/dev` - For Remix consumers migrating to React Router, the Vite plugin's `manifest` option has been removed ([#11573](https://github.com/remix-run/react-router/pull/11573)
    )
*   `@react-router/dev` - Update default `isbot` version to v5 and drop support for `isbot@3` ([#11770](https://github.com/remix-run/react-router/pull/11770)
    )
    *   If you have `isbot@4` or `isbot@5` in your `package.json`:
        *   You do not need to make any changes
    *   If you have `isbot@3` in your `package.json` and you have your own `entry.server.tsx` file in your repo
        *   You do not need to make any changes
        *   You can upgrade to `isbot@5` independent of the React Router v7 upgrade
    *   If you have `isbot@3` in your `package.json` and you do not have your own `entry.server.tsx` file in your repo
        *   You are using the internal default entry provided by React Router v7 and you will need to upgrade to `isbot@5` in your `package.json`
*   `@react-router/dev` - For Remix consumers migrating to React Router, Vite manifests (i.e. `.vite/manifest.json`) are now written within each build subdirectory, e.g. `build/client/.vite/manifest.json` and `build/server/.vite/manifest.json` instead of `build/.vite/client-manifest.json` and `build/.vite/server-manifest.json`. This means that the build output is now much closer to what you'd expect from a typical Vite project. ([#11573](https://github.com/remix-run/react-router/pull/11573)
    )
    *   Originally the Remix Vite plugin moved all Vite manifests to a root-level `build/.vite` directory to avoid accidentally serving them in production, particularly from the client build. This was later improved with additional logic that deleted these Vite manifest files at the end of the build process unless Vite's `build.manifest` had been enabled within the app's Vite config. This greatly reduced the risk of accidentally serving the Vite manifests in production since they're only present when explicitly asked for. As a result, we can now assume that consumers will know that they need to manage these additional files themselves, and React Router can safely generate a more standard Vite build output.

### [](#minor-changes-6)
Minor Changes

*   `react-router` - Params, loader data, and action data as props for route component exports ([#11961](https://github.com/remix-run/react-router/pull/11961)
    )
*   `react-router` - Add route module type generation ([#12019](https://github.com/remix-run/react-router/pull/12019)
    )
*   `react-router` - Remove duplicate `RouterProvider` implementations ([#11679](https://github.com/remix-run/react-router/pull/11679)
    )
*   `react-router` - Stabilize `unstable_dataStrategy` ([#11969](https://github.com/remix-run/react-router/pull/11969)
    )
*   `react-router` - Stabilize `unstable_patchRoutesOnNavigation` ([#11970](https://github.com/remix-run/react-router/pull/11970)
    )
*   `react-router` - Add prefetching support to `Link`/`NavLink` when using Remix SSR ([#11402](https://github.com/remix-run/react-router/pull/11402)
    )
*   `react-router` - Enhance `ScrollRestoration` so it can restore properly on an SSR'd document load ([#11401](https://github.com/remix-run/react-router/pull/11401)
    )
*   `@react-router/dev` - Add support for the `prerender` config in the React Router vite plugin, to support existing SSG use-cases ([#11539](https://github.com/remix-run/react-router/pull/11539)
    )
*   `@react-router/dev` - Remove internal `entry.server.spa.tsx` implementation which was not compatible with the Single Fetch async hydration approach ([#11681](https://github.com/remix-run/react-router/pull/11681)
    )
*   `@react-router/serve`: Update `express.static` configurations to support new `prerender` API ([#11547](https://github.com/remix-run/react-router/pull/11547)
    )
    *   Assets in the `build/client/assets` folder are served as before, with a 1-year immutable `Cache-Control` header
    *   Static files outside of assets, such as pre-rendered `.html` and `.data` files are not served with a specific `Cache-Control` header
    *   `.data` files are served with `Content-Type: text/x-turbo`
        *   For some reason, when adding this via `express.static`, it seems to also add a `Cache-Control: public, max-age=0` to `.data` files

### [](#patch-changes-17)
Patch Changes

*   Replace `substr` with `substring` ([#12080](https://github.com/remix-run/react-router/pull/12080)
    )
*   `react-router` - Fix redirects returned from loaders/actions using `data()` ([#12021](https://github.com/remix-run/react-router/pull/12021)
    )
*   `@react-router/dev` - Enable prerendering for resource routes ([#12200](https://github.com/remix-run/react-router/pull/12200)
    )
*   `@react-router/dev` - resolve config directory relative to flat output file structure ([#12187](https://github.com/remix-run/react-router/pull/12187)
    )

### [](#changes-by-package-6)
Changes by Package

*   [`react-router`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router/CHANGELOG.md#700)
    
*   [`@react-router/architect`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-architect/CHANGELOG.md#700)
    
*   [`@react-router/cloudflare`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-cloudflare/CHANGELOG.md#700)
    
*   [`@react-router/dev`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-dev/CHANGELOG.md#700)
    
*   [`@react-router/express`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-express/CHANGELOG.md#700)
    
*   [`@react-router/fs-routes`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-fs-routes/CHANGELOG.md#700)
    
*   [`@react-router/node`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-node/CHANGELOG.md#700)
    
*   [`@react-router/remix-config-routes-adapter`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-remix-config-routes-adapter/CHANGELOG.md#700)
    
*   [`@react-router/serve`](https://github.com/remix-run/react-router/blob/react-router%407.0.0/packages/react-router-serve/CHANGELOG.md#700)
    

**Full Changelog**: [`v6.28.0...v7.0.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@7.0.0)

[](#react-router-v6-releases)
React Router v6 Releases
======================================================

[](#v6300)
v6.30.0
------------------

Date: 2025-02-27

### [](#minor-changes-7)
Minor Changes

*   Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13109](https://github.com/remix-run/react-router/pull/13109)
    )

### [](#patch-changes-18)
Patch Changes

*   Fix regression introduced in `6.29.0` via [#12169](https://github.com/remix-run/react-router/pull/12169)
     that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#13108](https://github.com/remix-run/react-router/pull/13108)
    )

**Full Changelog**: [`v6.29.0...v6.30.0`](https://github.com/remix-run/react-router/compare/react-router@6.29.0...react-router@6.30.0)

[](#v6290)
v6.29.0
------------------

Date: 2025-01-30

### [](#minor-changes-8)
Minor Changes

*   Provide the request `signal` as a parameter to `patchRoutesOnNavigation` ([#12900](https://github.com/remix-run/react-router/pull/12900)
    )
    *   This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted

### [](#patch-changes-19)
Patch Changes

*   Do not log v7 deprecation warnings in production builds ([#12794](https://github.com/remix-run/react-router/pull/12794)
    )
*   Properly bubble headers when throwing a `data()` result ([#12845](https://github.com/remix-run/react-router/pull/12845)
    )
*   Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12169](https://github.com/remix-run/react-router/pull/12169)
    )
*   Strip search parameters from `patchRoutesOnNavigation` `path` param for fetcher calls ([#12899](https://github.com/remix-run/react-router/pull/12899)
    )

**Full Changelog**: [`v6.28.2...v6.29.0`](https://github.com/remix-run/react-router/compare/react-router@6.28.2...react-router@6.29.0)

[](#v6282)
v6.28.2
------------------

Date: 2025-01-16

### [](#patch-changes-20)
Patch Changes

*   Fix manual fetcher `key` usage when not opted into `future.v7_fetcherPersist` ([#12674](https://github.com/remix-run/react-router/pull/12674)
    )
*   Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12674](https://github.com/remix-run/react-router/pull/12674)
    )

**Full Changelog**: [`v6.28.1...v6.28.2`](https://github.com/remix-run/react-router/compare/react-router@6.28.1...react-router@6.28.2)

[](#v6281)
v6.28.1
------------------

Date: 2024-12-20

### [](#patch-changes-21)
Patch Changes

*   Allow users to opt out of v7 deprecation warnings by setting flags to `false` ([#12441](https://github.com/remix-run/react-router/pull/12441)
    )

**Full Changelog**: [`v6.28.0...v6.28.1`](https://github.com/remix-run/react-router/compare/react-router@6.28.0...react-router@6.28.1)

[](#v6280)
v6.28.0
------------------

Date: 2024-11-06

### [](#whats-changed-3)
What's Changed

*   In preparation for v7 we've added deprecation warnings for any future flags that you have not yet opted into. Please use the flags to better prepare for eventually upgrading to v7.

### [](#minor-changes-9)
Minor Changes

*   Log deprecation warnings for v7 flags ([#11750](https://github.com/remix-run/react-router/pull/11750)
    )
    *   Add deprecation warnings to `json`/`defer` in favor of returning raw objects
        *   These methods will be removed in React Router v7

### [](#patch-changes-22)
Patch Changes

*   Update JSDoc URLs for new website structure (add /v6/ segment) ([#12141](https://github.com/remix-run/react-router/pull/12141)
    )

**Full Changelog**: [`v6.27.0...v6.28.0`](https://github.com/remix-run/react-router/compare/react-router@6.27.0...react-router@6.28.0)

[](#v6270)
v6.27.0
------------------

Date: 2024-10-11

### [](#whats-changed-4)
What's Changed

#### [](#stabilized-apis)
Stabilized APIs

This release stabilizes a handful of "unstable" APIs in preparation for the [pending](https://x.com/remix_run/status/1841926034868077009)
 React Router v7 release (see [these](https://remix.run/blog/merging-remix-and-react-router)
 [posts](https://remix.run/blog/incremental-path-to-react-19)
 for more info):

*   `unstable_dataStrategy` → `dataStrategy` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optsdatastrategy)
    )
*   `unstable_patchRoutesOnNavigation` → `patchRoutesOnNavigation` (`createBrowserRouter` and friends) ([Docs](https://reactrouter.com/v6/routers/create-browser-router#optspatchroutesonnavigation)
    )
*   `unstable_flushSync` → `flushSync` (`useSubmit`, `fetcher.load`, `fetcher.submit`) ([Docs](https://reactrouter.com/v6/hooks/use-submit#optionsflushsync)
    )
*   `unstable_viewTransition` → `viewTransition` (`<Link>`, `<Form>`, `useNavigate`, `useSubmit`) ([Docs](https://reactrouter.com/v6/components/link#viewtransition)
    )

### [](#minor-changes-10)
Minor Changes

*   Stabilize the `unstable_flushSync` option for navigations and fetchers ([#11989](https://github.com/remix-run/react-router/pull/11989)
    )
*   Stabilize the `unstable_viewTransition` option for navigations and the corresponding `unstable_useViewTransitionState` hook ([#11989](https://github.com/remix-run/react-router/pull/11989)
    )
*   Stabilize `unstable_dataStrategy` ([#11974](https://github.com/remix-run/react-router/pull/11974)
    )
*   Stabilize `unstable_patchRoutesOnNavigation` ([#11973](https://github.com/remix-run/react-router/pull/11973)
    )
    *   Add new `PatchRoutesOnNavigationFunctionArgs` type for convenience ([#11967](https://github.com/remix-run/react-router/pull/11967)
        )

### [](#patch-changes-23)
Patch Changes

*   Fix bug when submitting to the current contextual route (parent route with an index child) when an `?index` param already exists from a prior submission ([#12003](https://github.com/remix-run/react-router/pull/12003)
    )
*   Fix `useFormAction` bug - when removing `?index` param it would not keep other non-Remix `index` params ([#12003](https://github.com/remix-run/react-router/pull/12003)
    )
*   Fix bug with fetchers not persisting `preventScrollReset` through redirects during concurrent fetches ([#11999](https://github.com/remix-run/react-router/pull/11999)
    )
*   Avoid unnecessary `console.error` on fetcher abort due to back-to-back revalidation calls ([#12050](https://github.com/remix-run/react-router/pull/12050)
    )
*   Fix bugs with `partialHydration` when hydrating with errors ([#12070](https://github.com/remix-run/react-router/pull/12070)
    )
*   Remove internal cache to fix issues with interrupted `patchRoutesOnNavigation` calls ([#12055](https://github.com/remix-run/react-router/pull/12055)
    )
    *   ⚠️ This may be a breaking change if you were relying on this behavior in the `unstable_` API
    *   We used to cache in-progress calls to `patchRoutesOnNavigation` internally so that multiple navigations with the same start/end would only execute the function once and use the same promise
    *   However, this approach was at odds with `patch` short circuiting if a navigation was interrupted (and the `request.signal` aborted) since the first invocation's `patch` would no-op
    *   This cache also made some assumptions as to what a valid cache key might be - and is oblivious to any other application-state changes that may have occurred
    *   So, the cache has been removed because in _most_ cases, repeated calls to something like `import()` for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userland
*   Remove internal `discoveredRoutes` FIFO queue from `unstable_patchRoutesOnNavigation` ([#11977](https://github.com/remix-run/react-router/pull/11977)
    )
    *   ⚠️ This may be a breaking change if you were relying on this behavior in the `unstable_` API
    *   This was originally implemented as an optimization but it proved to be a bit too limiting
    *   If you need this optimization you can implement your own cache inside `patchRoutesOnNavigation`
*   Fix types for `RouteObject` within `PatchRoutesOnNavigationFunction`'s `patch` method so it doesn't expect agnostic route objects passed to `patch` ([#11967](https://github.com/remix-run/react-router/pull/11967)
    )
*   Expose errors thrown from `patchRoutesOnNavigation` directly to `useRouteError` instead of wrapping them in a 400 `ErrorResponse` instance ([#12111](https://github.com/remix-run/react-router/pull/12111)
    )

**Full Changelog**: [`v6.26.2...v6.27.0`](https://github.com/remix-run/react-router/compare/react-router@6.26.2...react-router@6.27.0)

[](#v6262)
v6.26.2
------------------

Date: 2024-09-09

### [](#patch-changes-24)
Patch Changes

*   Update the `unstable_dataStrategy` API to allow for more advanced implementations ([#11943](https://github.com/remix-run/react-router/pull/11943)
    )
    *   ⚠️ If you have already adopted `unstable_dataStrategy`, please review carefully as this includes breaking changes to this API
    *   Rename `unstable_HandlerResult` to `unstable_DataStrategyResult`
    *   Change the return signature of `unstable_dataStrategy` from a parallel array of `unstable_DataStrategyResult[]` (parallel to `matches`) to a key/value object of `routeId => unstable_DataStrategyResult`
        *   This allows more advanced control over revalidation behavior because you can opt-into or out-of revalidating data that may not have been revalidated by default (via `match.shouldLoad`)
    *   You should now return/throw a result from your `handlerOverride` instead of returning a `DataStrategyResult`
        *   The return value (or thrown error) from your `handlerOverride` will be wrapped up into a `DataStrategyResult` and returned fromm `match.resolve`
        *   Therefore, if you are aggregating the results of `match.resolve()` into a final results object you should not need to think about the `DataStrategyResult` type
        *   If you are manually filling your results object from within your `handlerOverride`, then you will need to assign a `DataStrategyResult` as the value so React Router knows if it's a successful execution or an error (see examples in the documentation for details)
    *   Added a new `fetcherKey` parameter to `unstable_dataStrategy` to allow differentiation from navigational and fetcher calls
*   Preserve opted-in view transitions through redirects ([#11925](https://github.com/remix-run/react-router/pull/11925)
    )
*   Preserve pending view transitions through a router revalidation call ([#11917](https://github.com/remix-run/react-router/pull/11917)
    )
*   Fix blocker usage when `blocker.proceed` is called quickly/synchronously ([#11930](https://github.com/remix-run/react-router/pull/11930)
    )

**Full Changelog**: [`v6.26.1...v6.26.2`](https://github.com/remix-run/react-router/compare/react-router@6.26.1...react-router@6.26.2)

[](#v6261)
v6.26.1
------------------

Date: 2024-08-15

### [](#patch-changes-25)
Patch Changes

*   Rename `unstable_patchRoutesOnMiss` to `unstable_patchRoutesOnNavigation` to match new behavior ([#11888](https://github.com/remix-run/react-router/pull/11888)
    )
*   Update `unstable_patchRoutesOnNavigation` logic so that we call the method when we match routes with dynamic param or splat segments in case there exists a higher-scoring static route that we've not yet discovered ([#11883](https://github.com/remix-run/react-router/pull/11883)
    )
    *   We also now leverage an internal FIFO queue of previous paths we've already called `unstable_patchRoutesOnNavigation` against so that we don't re-call on subsequent navigations to the same path

**Full Changelog**: [`v6.26.0...v6.26.1`](https://github.com/remix-run/react-router/compare/react-router@6.26.0...react-router@6.26.1)

[](#v6260)
v6.26.0
------------------

Date: 2024-08-01

### [](#minor-changes-11)
Minor Changes

*   Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://github.com/remix-run/react-router/pull/11811)
    )
*   Add a new `unstable_data()` API for usage with Remix Single Fetch ([#11836](https://github.com/remix-run/react-router/pull/11836)
    )
    *   This API is not intended for direct usage in React Router SPA applications
    *   It is primarily intended for usage with `createStaticHandler.query()` to allow loaders/actions to return arbitrary data along with custom `status`/`headers` without forcing the serialization of data into a `Response` instance
    *   This allows for more advanced serialization tactics via `unstable_dataStrategy` such as serializing via `turbo-stream` in Remix Single Fetch
    *   ⚠️ This removes the `status` field from `HandlerResult`
        *   If you need to return a specific `status` from `unstable_dataStrategy` you should instead do so via `unstable_data()`

### [](#patch-changes-26)
Patch Changes

*   Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations ([#11839](https://github.com/remix-run/react-router/pull/11839)
    )
*   Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838)
    )
    *   During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components

**Full Changelog**: [`v6.25.1...v6.26.0`](https://github.com/remix-run/react-router/compare/react-router@6.25.1...react-router@6.26.0)

[](#v6251)
v6.25.1
------------------

Date: 2024-07-17

### [](#patch-changes-27)
Patch Changes

*   Memoize some `RouterProvider` internals to reduce unnecessary re-renders ([#11803](https://github.com/remix-run/react-router/pull/11803)
    )

**Full Changelog**: [`v6.25.0...v6.25.1`](https://github.com/remix-run/react-router/compare/react-router@6.25.0...react-router@6.25.1)

[](#v6250)
v6.25.0
------------------

Date: 2024-07-16

### [](#whats-changed-5)
What's Changed

#### [](#stabilized-v7_skipactionerrorrevalidation)
Stabilized `v7_skipActionErrorRevalidation`

This release stabilizes the `future.unstable_skipActionErrorRevalidation` flag into [`future.v7_skipActionErrorRevalidation`](https://reactrouter.com/v6/upgrading/future#v7_skipactionstatusrevalidation)
 in preparation for the upcoming React Router v7 release.

*   When this flag is enabled, actions that return/throw a `4xx/5xx` `Response` will not trigger a revalidation by default
*   This also stabilizes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus`

### [](#minor-changes-12)
Minor Changes

*   Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769)
    )

### [](#patch-changes-28)
Patch Changes

*   Fix regression and properly decode paths inside `useMatch` so matches/params reflect decoded params ([#11789](https://github.com/remix-run/react-router/pull/11789)
    )
*   Fix bubbling of errors thrown from `unstable_patchRoutesOnMiss` ([#11786](https://github.com/remix-run/react-router/pull/11786)
    )
*   Fix hydration in SSR apps using `unstable_patchRoutesOnMiss` that matched a splat route on the server ([#11790](https://github.com/remix-run/react-router/pull/11790)
    )

**Full Changelog**: [`v6.24.1...v6.25.0`](https://github.com/remix-run/react-router/compare/react-router@6.24.1...react-router@6.25.0)

[](#v6241)
v6.24.1
------------------

Date: 2024-07-03

### [](#patch-changes-29)
Patch Changes

*   Remove `polyfill.io` reference from warning message because the domain was sold and has since been determined to serve malware ([#11741](https://github.com/remix-run/react-router/pull/11741)
    )
    *   See [https://sansec.io/research/polyfill-supply-chain-attack](https://sansec.io/research/polyfill-supply-chain-attack)
        
*   Export `NavLinkRenderProps` type for easier typing of custom `NavLink` callback ([#11553](https://github.com/remix-run/react-router/pull/11553)
    )
*   When using `future.v7_relativeSplatPath`, properly resolve relative paths in splat routes that are children of pathless routes ([#11633](https://github.com/remix-run/react-router/pull/11633)
    )
*   Fog of War (unstable): Trigger a new `router.routes` identity/reflow during route patching ([#11740](https://github.com/remix-run/react-router/pull/11740)
    )
*   Fog of War (unstable): Fix initial matching when a splat route matches ([#11759](https://github.com/remix-run/react-router/pull/11759)
    )

**Full Changelog**: [`v6.24.0...v6.24.1`](https://github.com/remix-run/react-router/compare/react-router@6.24.0...react-router@6.24.1)

[](#v6240)
v6.24.0
------------------

Date: 2024-06-24

### [](#whats-changed-6)
What's Changed

#### [](#lazy-route-discovery-aka-fog-of-war)
Lazy Route Discovery (a.k.a. "Fog of War")

We're really excited to release our new API for "Lazy Route Discovery" in `v6.24.0`! For some background information, please check out the original [RFC](https://github.com/remix-run/react-router/discussions/11113)
. The **tl;dr;** is that ever since we introduced the Data APIs in v6.4 via `<RouterProvider>`, we've been a little bummed that one of the tradeoffs was the lack of a compelling code-splitting story mirroring what we had in the `<BrowserRouter>`/`<Routes>` apps. We took a baby-step towards improving that story with `route.lazy` in `v6.9.0`, but with `v6.24.0` we've gone the rest of the way.

With "Fog of War", you can now load portions of the route tree lazily via the new `unstable_patchRoutesOnMiss` option passed to `createBrowserRouter` (and it's memory/hash counterparts). This gives you a way to hook into spots where React Router is unable to match a given path and patch new routes into the route tree during the navigation (or fetcher call).

Here's a very small example, but please refer to the [documentation](https://reactrouter.com/v6/routers/create-browser-router#optsunstable_patchroutesonmiss)
 for more information and use cases:

    const router = createBrowserRouter(
      [\
        {\
          id: "root",\
          path: "/",\
          Component: RootComponent,\
        },\
      ],
      {
        async unstable_patchRoutesOnMiss({ path, patch }) {
          if (path === "/a") {
            // Load the `a` route (`{ path: 'a', Component: A }`)
            let route = await getARoute();
            // Patch the `a` route in as a new child of the `root` route
            patch("root", [route]);
          }
        },
      }
    );
    

### [](#minor-changes-13)
Minor Changes

*   Add support for Lazy Route Discovery (a.k.a. "Fog of War") ([#11626](https://github.com/remix-run/react-router/pull/11626)
    )

### [](#patch-changes-30)
Patch Changes

*   Fix `fetcher.submit` types - remove incorrect `navigate`/`fetcherKey`/`unstable_viewTransition` options because they are only relevant for `useSubmit` ([#11631](https://github.com/remix-run/react-router/pull/11631)
    )
*   Allow falsy `location.state` values passed to `<StaticRouter>` ([#11495](https://github.com/remix-run/react-router/pull/11495)
    )

**Full Changelog**: [`v6.23.1...v6.24.0`](https://github.com/remix-run/react-router/compare/react-router@6.23.1...react-router@6.24.0)

[](#v6231)
v6.23.1
------------------

Date: 2024-05-10

### [](#patch-changes-31)
Patch Changes

*   Allow `undefined` to be resolved through `<Await>` ([#11513](https://github.com/remix-run/react-router/pull/11513)
    )
*   Add defensive `document` check when checking for `document.startViewTransition` availability ([#11544](https://github.com/remix-run/react-router/pull/11544)
    )
*   Change the `react-router-dom/server` import back to `react-router-dom` instead of `index.ts` ([#11514](https://github.com/remix-run/react-router/pull/11514)
    )
*   `@remix-run/router` - Support `unstable_dataStrategy` on `staticHandler.queryRoute` ([#11515](https://github.com/remix-run/react-router/pull/11515)
    )

**Full Changelog**: [`v6.23.0...v6.23.1`](https://github.com/remix-run/react-router/compare/react-router@6.23.0...react-router@6.23.1)

[](#v6230)
v6.23.0
------------------

Date: 2024-04-23

### [](#whats-changed-7)
What's Changed

#### [](#data-strategy-unstable)
Data Strategy (unstable)

The new `unstable_dataStrategy` API is a low-level API designed for advanced use-cases where you need to take control over the data strategy for your `loader`/`action` functions. The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix ["Single Fetch"](https://remix.run/docs/guides/single-fetch)
, user-land middleware/context APIs, automatic loader caching, and more. Please see the [docs](https://reactrouter.com/v6/routers/create-browser-router#unstable_datastrategy)
 for more information.

**Note:** This is a low-level API intended for advanced use-cases. This overrides React Router's internal handling of `loader`/`action` execution, and if done incorrectly will break your app code. Please use with caution and perform the appropriate testing.

#### [](#skip-action-error-revalidation-unstable)
Skip Action Error Revalidation (unstable)

Currently, all active `loader`'s revalidate after any `action` submission, regardless of the `action` result. However, in the majority of cases a `4xx`/`5xx` response from an `action` means that no data was actually changed and the revalidation is unnecessary. We've introduced a new `future.unstable_skipActionErrorRevalidation` flag that changes the behavior here, and we plan to make this the default in future version of React Router.

With this flag enabled, `action`'s that return/throw a `4xx`/`5xx` response status will no longer automatically revalidate. If you need to revalidate after a `4xx`/`5xx` result with this flag enabled, you can still do that via returning `true` from `shouldRevalidate` - which now also receives a new `unstable_actionStatus` argument alongside `actionResult` so you can make decision based on the status of the `action` response without having to encode it into the action data.

### [](#minor-changes-14)
Minor Changes

*   Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098)
    , [#11377](https://github.com/remix-run/react-router/pull/11377)
    )
*   `@remix-run/router` - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098)
    )
*   `@remix-run/router` - SSR: Added a new `skipLoaderErrorBubbling` options to the `staticHandler.query` method to disable error bubbling by the static handler for use in Remix's Single Fetch implementation ([#11098](https://github.com/remix-run/react-router/pull/11098)
    , ([#11377](https://github.com/remix-run/react-router/pull/11377)
    ))

**Full Changelog**: [`v6.22.3...v6.23.0`](https://github.com/remix-run/react-router/compare/react-router@6.22.3...react-router@6.23.0)

[](#v6223)
v6.22.3
------------------

Date: 2024-03-07

### [](#patch-changes-32)
Patch Changes

*   Fix a `future.v7_partialHydration` bug that would re-run loaders below the boundary on hydration if SSR loader errors bubbled to a parent boundary ([#11324](https://github.com/remix-run/react-router/pull/11324)
    )
*   Fix a `future.v7_partialHydration` bug that would consider the router uninitialized if a route did not have a loader ([#11325](https://github.com/remix-run/react-router/pull/11325)
    )

**Full Changelog**: [`v6.22.2...v6.22.3`](https://github.com/remix-run/react-router/compare/react-router@6.22.2...react-router@6.22.3)

[](#v6222)
v6.22.2
------------------

Date: 2024-02-28

### [](#patch-changes-33)
Patch Changes

*   Preserve hydrated errors during partial hydration runs ([#11305](https://github.com/remix-run/react-router/pull/11305)
    )

**Full Changelog**: [`v6.22.1...v6.22.2`](https://github.com/remix-run/react-router/compare/react-router@6.22.1...react-router@6.22.2)

[](#v6221)
v6.22.1
------------------

Date: 2024-02-16

### [](#patch-changes-34)
Patch Changes

*   Fix encoding/decoding issues with pre-encoded dynamic parameter values ([#11199](https://github.com/remix-run/react-router/pull/11199)
    )

**Full Changelog**: [`v6.22.0...v6.22.1`](https://github.com/remix-run/react-router/compare/react-router@6.22.0...react-router@6.22.1)

[](#v6220)
v6.22.0
------------------

Date: 2024-02-01

### [](#whats-changed-8)
What's Changed

#### [](#core-web-vitals-technology-report-flag)
Core Web Vitals Technology Report Flag

In 2021, the HTTP Archive launched the [Core Web Vitals Technology Report dashboard](https://discuss.httparchive.org/t/new-dashboard-the-core-web-vitals-technology-report/2178)
:

> By combining the powers of real-user experiences in the Chrome UX Report 26 (CrUX) dataset with web technology detections in HTTP Archive 30, we can get a glimpse into how architectural decisions like choices of CMS platform or JavaScript framework play a role in sites’ CWV performance.

They use a tool called [`wappalyzer`](https://github.com/HTTPArchive/wappalyzer)
 to identify what technologies a given website is using by looking for certain scripts, global JS variables, or other identifying characteristics. For example, for Remix applications, they [look for the global `__remixContext`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L1328)
 variable to identify that a website is using Remix.

It was brought to our attention that React Router was unable to be reliably identified because there are no identifying global aspects. They are currently [looking for external scripts with `react-router`](https://github.com/HTTPArchive/wappalyzer/blob/c2a24ee7c2d07bf9c521f02584ae2dcf603ac0b7/src/technologies/r.json#L637)
 in the name. This will identify sites using React Router from a CDN such as `unpkg` - but it will miss the **vast** majority of sites that are installing React Router from the npm registry and bundling it into their JS files. This results in [drastically under-reporting](https://lookerstudio.google.com/s/pixHkNmGbN4)
 the usage of React Router on the web.

Starting with version `6.22.0`, sites using `react-router-dom` will begin adding a `window.__reactRouterVersion` variable that will be set to a string value of the SemVer major version number (i.e., `window.__reactRouterVersion = "6";`) so that they can be properly identified.

### [](#minor-changes-15)
Minor Changes

*   Include a `window.__reactRouterVersion` for CWV Report detection ([#11222](https://github.com/remix-run/react-router/pull/11222)
    )
*   Add a `createStaticHandler` `future.v7_throwAbortReason` flag to throw `request.signal.reason` (defaults to a `DOMException`) when a request is aborted instead of an `Error` such as `new Error("query() call aborted: GET /path")` ([#11104](https://github.com/remix-run/react-router/pull/11104)
    )
    *   Please note that `DOMException` was added in Node v17 so you will not get a `DOMException` on Node 16 and below.

### [](#patch-changes-35)
Patch Changes

*   Respect the `ErrorResponse` status code if passed to `getStaticContextFormError` ([#11213](https://github.com/remix-run/react-router/pull/11213)
    )

**Full Changelog**: [`v6.21.3...v6.22.0`](https://github.com/remix-run/react-router/compare/react-router@6.21.3...react-router@6.22.0)

[](#v6213)
v6.21.3
------------------

Date: 2024-01-18

### [](#patch-changes-36)
Patch Changes

*   Fix `NavLink` `isPending` when a `basename` is used ([#11195](https://github.com/remix-run/react-router/pull/11195)
    )
*   Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://github.com/remix-run/react-router/pull/11187)
    )

**Full Changelog**: [`v6.21.2...v6.21.3`](https://github.com/remix-run/react-router/compare/react-router@6.21.2...react-router@6.21.3)

[](#v6212)
v6.21.2
------------------

Date: 2024-01-11

### [](#patch-changes-37)
Patch Changes

*   Leverage `useId` for internal fetcher keys when available ([#11166](https://github.com/remix-run/react-router/pull/11166)
    )
*   Fix bug where dashes were not picked up in dynamic parameter names ([#11160](https://github.com/remix-run/react-router/pull/11160)
    )
*   Do not attempt to deserialize empty JSON responses ([#11164](https://github.com/remix-run/react-router/pull/11164)
    )

**Full Changelog**: [`v6.21.1...v6.21.2`](https://github.com/remix-run/react-router/compare/react-router@6.21.1...react-router@6.21.2)

[](#v6211)
v6.21.1
------------------

Date: 2023-12-21

### [](#patch-changes-38)
Patch Changes

*   Fix bug with `route.lazy` not working correctly on initial SPA load when `v7_partialHydration` is specified ([#11121](https://github.com/remix-run/react-router/pull/11121)
    )
*   Fix bug preventing revalidation from occurring for persisted fetchers unmounted during the `submitting` phase ([#11102](https://github.com/remix-run/react-router/pull/11102)
    )
*   De-dup relative path logic in `resolveTo` ([#11097](https://github.com/remix-run/react-router/pull/11097)
    )

**Full Changelog**: [`v6.21.0...v6.21.1`](https://github.com/remix-run/react-router/compare/react-router@6.21.0...react-router@6.21.1)

[](#v6210)
v6.21.0
------------------

Date: 2023-12-13

### [](#whats-changed-9)
What's Changed

#### [](#futurev7_relativesplatpath)
`future.v7_relativeSplatPath`

We fixed a splat route path-resolution bug in `6.19.0`, but later determined a large number of applications were relying on the buggy behavior, so we reverted the fix in `6.20.1` (see [#10983](https://github.com/remix-run/react-router/issues/10983)
, [#11052](https://github.com/remix-run/react-router/issues/11052)
, [#11078](https://github.com/remix-run/react-router/issues/11078)
).

The buggy behavior is that the default behavior when resolving relative paths inside a splat route would _ignore_ any splat (`*`) portion of the current route path. When the future flag is enabled, splat portions are included in relative path logic within splat routes.

For more information, please refer to the [`useResolvedPath` docs](https://reactrouter.com/v6/hooks/use-resolved-path#splat-paths)
 and/or the [detailed changelog entry](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md#6210)
.

#### [](#partial-hydration)
Partial Hydration

We added a new `future.v7_partialHydration` future flag for the `@remix-run/router` that enables partial hydration of a data router when Server-Side Rendering. This allows you to provide `hydrationData.loaderData` that has values for _some_ initially matched route loaders, but not all. When this flag is enabled, the router will call `loader` functions for routes that do not have hydration loader data during `router.initialize()`, and it will render down to the deepest provided `HydrateFallback` (up to the first route without hydration data) while it executes the unhydrated routes. ([#11033](https://github.com/remix-run/react-router/pull/11033)
)

### [](#minor-changes-16)
Minor Changes

*   Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087)
    )
*   Add a new `future.v7_partialHydration` future flag that enables partial hydration of a data router when Server-Side Rendering ([#11033](https://github.com/remix-run/react-router/pull/11033)
    )

### [](#patch-changes-39)
Patch Changes

*   Properly handle falsy error values in `ErrorBoundary`'s ([#11071](https://github.com/remix-run/react-router/pull/11071)
    )
*   Catch and bubble errors thrown when trying to unwrap responses from `loader`/`action` functions ([#11061](https://github.com/remix-run/react-router/pull/11061)
    )
*   Fix `relative="path"` issue when rendering `Link`/`NavLink` outside of matched routes ([#11062](https://github.com/remix-run/react-router/pull/11062)
    )

**Full Changelog**: [`v6.20.1...v6.21.0`](https://github.com/remix-run/react-router/compare/react-router@6.20.1...react-router@6.21.0)

[](#v6201)
v6.20.1
------------------

Date: 2023-12-01

### [](#patch-changes-40)
Patch Changes

*   Revert the `useResolvedPath` fix for splat routes due to a large number of applications that were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
    ) ([#11078](https://github.com/remix-run/react-router/pull/11078)
    )
    *   We plan to re-introduce this fix behind a future flag in the next minor version (see [this comment](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
        )
    *   This fix was included in versions `6.19.0` and `6.20.0`. If you are upgrading from `6.18.0` or earlier, you would not have been impacted by this fix.

**Full Changelog**: [`v6.20.0...v6.20.1`](https://github.com/remix-run/react-router/compare/react-router@6.20.0...react-router@6.20.1)

[](#v6200)
v6.20.0
------------------

Date: 2023-11-22

> \[!WARNING\] Please use version `6.20.1` or later instead of `6.20.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#11045](https://github.com/remix-run/react-router/pull/11045)
> ). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
>  for more details.

### [](#minor-changes-17)
Minor Changes

*   Export the `PathParam` type from the public API ([#10719](https://github.com/remix-run/react-router/pull/10719)
    )

### [](#patch-changes-41)
Patch Changes

*   Do not revalidate unmounted fetchers when `v7_fetcherPersist` is enabled ([#11044](https://github.com/remix-run/react-router/pull/11044)
    )
*   Fix bug with `resolveTo` path resolution in splat routes ([#11045](https://github.com/remix-run/react-router/pull/11045)
    )
    *   This is a follow up to [#10983](https://github.com/remix-run/react-router/pull/10983)
         to handle the few other code paths using `getPathContributingMatches`
    *   This removes the `UNSAFE_getPathContributingMatches` export from `@remix-run/router` since we no longer need this in the `react-router`/`react-router-dom` layers

**Full Changelog**: [`v6.19.0...v6.20.0`](https://github.com/remix-run/react-router/compare/react-router@6.19.0...react-router@6.20.0)

[](#v6190)
v6.19.0
------------------

Date: 2023-11-16

> \[!WARNING\] Please use version `6.20.1` or later instead of `6.19.0`. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release ([#10983](https://github.com/remix-run/react-router/pull/10983)
> ). We reverted the fix in `6.20.1` and will be re-introducing it behind a future flag in a subsequent release. See [#11052](https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329)
>  for more details.

### [](#whats-changed-10)
What's Changed

#### [](#unstable_flushsync-api)
`unstable_flushSync` API

This release brings a new `unstable_flushSync` option to the imperative APIs (`useSubmit`, `useNavigate`, `fetcher.submit`, `fetcher.load`) to let users opt-into synchronous DOM updates for pending/optimistic UI.

    function handleClick() {
      submit(data, { flushSync: true });
      // Everything is flushed to the DOM so you can focus/scroll to your pending/optimistic UI
      setFocusAndOrScrollToNewlyAddedThing();
    }
    

### [](#minor-changes-18)
Minor Changes

*   Add `unstable_flushSync` option to `useNavigate`/`useSubmit`/`fetcher.load`/`fetcher.submit` to opt-out of `React.startTransition` and into `ReactDOM.flushSync` for state updates ([#11005](https://github.com/remix-run/react-router/pull/11005)
    )
*   Remove the `unstable_` prefix from the [`useBlocker`](https://reactrouter.com/v6/hooks/use-blocker)
     hook as it's been in use for enough time that we are confident in the API ([#10991](https://github.com/remix-run/react-router/pull/10991)
    )
    *   We do not plan to remove the prefix from `unstable_usePrompt` due to differences in how browsers handle `window.confirm` that prevent React Router from guaranteeing consistent/correct behavior

### [](#patch-changes-42)
Patch Changes

*   Fix `useActionData` so it returns proper contextual action data and not _any_ action data in the tree ([#11023](https://github.com/remix-run/react-router/pull/11023)
    )
    
*   Fix bug in `useResolvedPath` that would cause `useResolvedPath(".")` in a splat route to lose the splat portion of the URL path. ([#10983](https://github.com/remix-run/react-router/pull/10983)
    )
    
    *   ⚠️ This fixes a quite long-standing bug specifically for `"."` paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via `"."` inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.
*   Fix issue where a changing fetcher `key` in a `useFetcher` that remains mounted wasn't getting picked up ([#11009](https://github.com/remix-run/react-router/pull/11009)
    )
    
*   Fix `useFormAction` which was incorrectly inheriting the `?index` query param from child route `action` submissions ([#11025](https://github.com/remix-run/react-router/pull/11025)
    )
    
*   Fix `NavLink` `active` logic when `to` location has a trailing slash ([#10734](https://github.com/remix-run/react-router/pull/10734)
    )
    
*   Fix types so `unstable_usePrompt` can accept a `BlockerFunction` in addition to a `boolean` ([#10991](https://github.com/remix-run/react-router/pull/10991)
    )
    
*   Fix `relative="path"` bug where relative path calculations started from the full location pathname, instead of from the current contextual route pathname. ([#11006](https://github.com/remix-run/react-router/pull/11006)
    )
    
        <Route path="/a">
          <Route path="/b" element={<Component />}>
            <Route path="/c" />
          </Route>
        </Route>;
        
        function Component() {
          return (
            <>
              {/* This is now correctly relative to /a/b, not /a/b/c */}
              <Link to=".." relative="path" />
              <Outlet />
            </>
          );
        }
        
    

**Full Changelog**: [`6.18.0...6.19.0`](https://github.com/remix-run/react-router/compare/react-router@6.18.0...react-router@6.19.0)

[](#v6180)
v6.18.0
------------------

Date: 2023-10-31

### [](#whats-changed-11)
What's Changed

#### [](#new-fetcher-apis)
New Fetcher APIs

Per this [RFC](https://github.com/remix-run/remix/discussions/7698)
, we've introduced some new APIs that give you more granular control over your fetcher behaviors.

*   You may now specify your own fetcher identifier via `useFetcher({ key: string })`, which allows you to access the same fetcher instance from different components in your application without prop-drilling
*   Fetcher keys are now exposed on the fetchers returned from `useFetchers` so that they can be looked up by `key`
*   `Form` and `useSubmit` now support optional `navigate`/`fetcherKey` props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified `key`
    *   `<Form method="post" navigate={false} fetcherKey="my-key">`
    *   `submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })`
    *   Invoking a fetcher in this way is ephemeral and stateless
    *   If you need to access the state of one of these fetchers, you will need to leverage `useFetchers()` or `useFetcher({ key })` to look it up elsewhere

#### [](#persistence-future-flag-futurev7_fetcherpersist)
Persistence Future Flag (`future.v7_fetcherPersist`)

Per the same [RFC](https://github.com/remix-run/remix/discussions/7698)
 as above, we've introduced a new `future.v7_fetcherPersist` flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an `idle` state. This makes pending/optimistic UI _much_ easier in scenarios where the originating fetcher needs to unmount.

*   This is sort of a long-standing bug fix as the `useFetchers()` API was always supposed to only reflect **in-flight** fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an `idle` state
*   Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
    *   Fetchers that complete _while still mounted_ will no longer appear in `useFetchers()` after completion - they served no purpose in there since you can access the data via `useFetcher().data`
    *   Fetchers that previously unmounted _while in-flight_ will not be immediately aborted and will instead be cleaned up once they return to an `idle` state
        *   They will remain exposed via `useFetchers` while in-flight so you can still access pending/optimistic data after unmount
        *   If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
        *   However, if a fetcher was re-mounted elsewhere in the tree using the same `key`, then it's result will be processed, even if the originating fetcher was unmounted

### [](#minor-changes-19)
Minor Changes

*   Add fetcher `key` APIs and `navigate=false` options ([#10960](https://github.com/remix-run/react-router/pull/10960)
    )
*   Add `future.v7_fetcherPersist` flag ([#10962](https://github.com/remix-run/react-router/pull/10962)
    )
*   Add support for optional path segments in `matchPath` ([#10768](https://github.com/remix-run/react-router/pull/10768)
    )

### [](#patch-changes-43)
Patch Changes

*   Fix the `future` prop on `BrowserRouter`, `HashRouter` and `MemoryRouter` so that it accepts a `Partial<FutureConfig>` instead of requiring all flags to be included ([#10962](https://github.com/remix-run/react-router/pull/10962)
    )
*   Fix `router.getFetcher`/`router.deleteFetcher` type definitions which incorrectly specified `key` as an optional parameter ([#10960](https://github.com/remix-run/react-router/pull/10960)
    )

**Full Changelog**: [`6.17.0...6.18.0`](https://github.com/remix-run/react-router/compare/react-router@6.17.0...react-router@6.18.0)

[](#v6170)
v6.17.0
------------------

Date: 2023-10-16

### [](#whats-changed-12)
What's Changed

#### [](#view-transitions-)
View Transitions 🚀

We're excited to release experimental support for the [View Transitions API](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition)
 in React Router! You can now trigger navigational DOM updates to be wrapped in `document.startViewTransition` to enable CSS animated transitions on SPA navigations in your application.

The simplest approach to enabling a View Transition in your React Router app is via the new [`<Link unstable_viewTransition>`](https://reactrouter.com/v6/components/link#unstable_viewtransition)
 prop. This will cause the navigation DOM update to be wrapped in `document.startViewTransition` which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

If you need to apply more fine-grained styles for your animations, you can leverage the [`unstable_useViewTransitionState`](https://reactrouter.com/v6/hooks/use-view-transition-state)
 hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

    function ImageLink(to, src, alt) {
      const isTransitioning = unstable_useViewTransitionState(to);
      return (
        <Link to={to} unstable_viewTransition>
          <img
            src={src}
            alt={alt}
            style={{
              viewTransitionName: isTransitioning ? "image-expand" : "",
            }}
          />
        </Link>
      );
    }
    

You can also use the [`<NavLink unstable_viewTransition>`](https://reactrouter.com/v6/components/nav-link#unstable_viewtransition)
 shorthand which will manage the hook usage for you and automatically add a `transitioning` class to the `<a>` during the transition:

    a.transitioning img {
      view-transition-name: "image-expand";
    }
    

    <NavLink to={to} unstable_viewTransition>
      <img src={src} alt={alt} />
    </NavLink>
    

For an example usage of View Transitions, check out [our fork](https://github.com/brophdawg11/react-router-records)
 of the awesome [Astro Records](https://github.com/Charca/astro-records)
 demo.

For more information on using the View Transitions API, please refer to the [Smooth and simple transitions with the View Transitions API](https://developer.chrome.com/docs/web-platform/view-transitions/)
 guide from the Google Chrome team.

### [](#minor-changes-20)
Minor Changes

*   Add support for view transitions ([#10916](https://github.com/remix-run/react-router/pull/10916)
    )

### [](#patch-changes-44)
Patch Changes

*   Log a warning and fail gracefully in `ScrollRestoration` when `sessionStorage` is unavailable ([#10848](https://github.com/remix-run/react-router/pull/10848)
    )
*   Fix `RouterProvider` `future` prop type to be a `Partial<FutureConfig>` so that not all flags must be specified ([#10900](https://github.com/remix-run/react-router/pull/10900)
    )
*   Allow 404 detection to leverage root route error boundary if path contains a URL segment ([#10852](https://github.com/remix-run/react-router/pull/10852)
    )
*   Fix `ErrorResponse` type to avoid leaking internal field ([#10876](https://github.com/remix-run/react-router/pull/10876)
    )

**Full Changelog**: [`6.16.0...6.17.0`](https://github.com/remix-run/react-router/compare/react-router@6.16.0...react-router@6.17.0)

[](#v6160)
v6.16.0
------------------

Date: 2023-09-13

### [](#minor-changes-21)
Minor Changes

*   In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of `any` with `unknown` on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to `any` in React Router and are overridden with `unknown` in Remix. In React Router v7 we plan to move these to `unknown` as a breaking change. ([#10843](https://github.com/remix-run/react-router/pull/10843)
    )
    *   `Location` now accepts a generic for the `location.state` value
    *   `ActionFunctionArgs`/`ActionFunction`/`LoaderFunctionArgs`/`LoaderFunction` now accept a generic for the `context` parameter (only used in SSR usages via `createStaticHandler`)
    *   The return type of `useMatches` (now exported as `UIMatch`) accepts generics for `match.data` and `match.handle` - both of which were already set to `unknown`
*   Move the `@private` class export `ErrorResponse` to an `UNSAFE_ErrorResponseImpl` export since it is an implementation detail and there should be no construction of `ErrorResponse` instances in userland. This frees us up to export a `type ErrorResponse` which correlates to an instance of the class via `InstanceType`. Userland code should only ever be using `ErrorResponse` as a type and should be type-narrowing via `isRouteErrorResponse`. ([#10811](https://github.com/remix-run/react-router/pull/10811)
    )
*   Export `ShouldRevalidateFunctionArgs` interface ([#10797](https://github.com/remix-run/react-router/pull/10797)
    )
*   Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (`_isFetchActionRedirect`, `_hasFetcherDoneAnything`) ([#10715](https://github.com/remix-run/react-router/pull/10715)
    )

### [](#patch-changes-45)
Patch Changes

*   Properly encode rendered URIs in server rendering to avoid hydration errors ([#10769](https://github.com/remix-run/react-router/pull/10769)
    )
*   Add method/url to error message on aborted `query`/`queryRoute` calls ([#10793](https://github.com/remix-run/react-router/pull/10793)
    )
*   Fix a race-condition with loader/action-thrown errors on `route.lazy` routes ([#10778](https://github.com/remix-run/react-router/pull/10778)
    )
*   Fix type for `actionResult` on the arguments object passed to `shouldRevalidate` ([#10779](https://github.com/remix-run/react-router/pull/10779)
    )

**Full Changelog**: [`v6.15.0...v6.16.0`](https://github.com/remix-run/react-router/compare/react-router@6.15.0...react-router@6.16.0)

[](#v6150)
v6.15.0
------------------

Date: 2023-08-10

### [](#minor-changes-22)
Minor Changes

*   Add's a new `redirectDocument()` function which allows users to specify that a redirect from a `loader`/`action` should trigger a document reload (via `window.location`) instead of attempting to navigate to the redirected location via React Router ([#10705](https://github.com/remix-run/react-router/pull/10705)
    )

### [](#patch-changes-46)
Patch Changes

*   Ensure `useRevalidator` is referentially stable across re-renders if revalidations are not actively occurring ([#10707](https://github.com/remix-run/react-router/pull/10707)
    )
*   Ensure hash history always includes a leading slash on hash pathnames ([#10753](https://github.com/remix-run/react-router/pull/10753)
    )
*   Fixes an edge-case affecting web extensions in Firefox that use `URLSearchParams` and the `useSearchParams` hook ([#10620](https://github.com/remix-run/react-router/pull/10620)
    )
*   Reorder effects in `unstable_usePrompt` to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously ([#10687](https://github.com/remix-run/react-router/pull/10687)
    , [#10718](https://github.com/remix-run/react-router/pull/10718)
    )
*   SSR: Do not include hash in `useFormAction()` for unspecified actions since it cannot be determined on the server and causes hydration issues ([#10758](https://github.com/remix-run/react-router/pull/10758)
    )
*   SSR: Fix an issue in `queryRoute` that was not always identifying thrown `Response` instances ([#10717](https://github.com/remix-run/react-router/pull/10717)
    )
*   `react-router-native`: Update `@ungap/url-search-params` dependency from `^0.1.4` to `^0.2.2` ([#10590](https://github.com/remix-run/react-router/pull/10590)
    )

**Full Changelog**: [`v6.14.2...v6.15.0`](https://github.com/remix-run/react-router/compare/react-router@6.14.2...react-router@6.15.0)

[](#v6142)
v6.14.2
------------------

Date: 2023-07-17

### [](#patch-changes-47)
Patch Changes

*   Add missing `<Form state>` prop to populate `history.state` on submission navigations ([#10630](https://github.com/remix-run/react-router/pull/10630)
    )
*   Trigger an error if a `defer` promise resolves/rejects with `undefined` in order to match the behavior of loaders and actions which must return a value or `null` ([#10690](https://github.com/remix-run/react-router/pull/10690)
    )
*   Properly handle fetcher redirects interrupted by normal navigations ([#10674](https://github.com/remix-run/react-router/pull/10674)
    )
*   Initial-load fetchers should not automatically revalidate on GET navigations ([#10688](https://github.com/remix-run/react-router/pull/10688)
    )
*   Properly decode element id when emulating hash scrolling via `<ScrollRestoration>` ([#10682](https://github.com/remix-run/react-router/pull/10682)
    )
*   Typescript: Enhance the return type of `Route.lazy` to prohibit returning an empty object ([#10634](https://github.com/remix-run/react-router/pull/10634)
    )
*   SSR: Support proper hydration of `Error` subclasses such as `ReferenceError`/`TypeError` ([#10633](https://github.com/remix-run/react-router/pull/10633)
    )

**Full Changelog**: [`v6.14.1...v6.14.2`](https://github.com/remix-run/react-router/compare/react-router@6.14.1...react-router@6.14.2)

[](#v6141)
v6.14.1
------------------

Date: 2023-06-30

### [](#patch-changes-48)
Patch Changes

*   Fix loop in `unstable_useBlocker` when used with an unstable blocker function ([#10652](https://github.com/remix-run/react-router/pull/10652)
    )
*   Fix issues with reused blockers on subsequent navigations ([#10656](https://github.com/remix-run/react-router/pull/10656)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.7.1`

**Full Changelog**: [`v6.14.0...v6.14.1`](https://github.com/remix-run/react-router/compare/react-router@6.14.0...react-router@6.14.1)

[](#v6140)
v6.14.0
------------------

Date: 2023-06-23

### [](#whats-changed-13)
What's Changed

#### [](#jsontext-submissions)
JSON/Text Submissions

`6.14.0` adds support for JSON and Text submissions via `useSubmit`/`fetcher.submit` since it's not always convenient to have to serialize into `FormData` if you're working in a client-side SPA. To opt-into these encodings you just need to specify the proper `formEncType`:

**Opt-into `application/json` encoding:**

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit({ key: "value" }, { method: "post", encType: "application/json" });
      // navigation.formEncType => "application/json"
      // navigation.json        => { key: "value" }
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "application/json"
      // await request.json()                => { key: "value" }
    }
    

**Opt-into `text/plain` encoding:**

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit("Text submission", { method: "post", encType: "text/plain" });
      // navigation.formEncType => "text/plain"
      // navigation.text        => "Text submission"
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "text/plain"
      // await request.text()                => "Text submission"
    }
    

**⚠️ Default Behavior Will Change in v7**

Please note that to avoid a breaking change, the default behavior will still encode a simple key/value JSON object into a `FormData` instance:

    function Component() {
      let navigation = useNavigation();
      let submit = useSubmit();
      submit({ key: "value" }, { method: "post" });
      // navigation.formEncType => "application/x-www-form-urlencoded"
      // navigation.formData    => FormData instance
    }
    
    async function action({ request }) {
      // request.headers.get("Content-Type") => "application/x-www-form-urlencoded"
      // await request.formData()            => FormData instance
    }
    

This behavior will likely change in v7 so it's best to make any JSON object submissions explicit with `formEncType: "application/x-www-form-urlencoded"` or `formEncType: "application/json"` to ease your eventual v7 migration path.

### [](#minor-changes-23)
Minor Changes

*   Add support for `application/json` and `text/plain` encodings for `useSubmit`/`fetcher.submit`. To reflect these additional types, `useNavigation`/`useFetcher` now also contain `navigation.json`/`navigation.text` and `fetcher.json`/`fetcher.text` which include the json/text submission if applicable. ([#10413](https://github.com/remix-run/react-router/pull/10413)
    )

### [](#patch-changes-49)
Patch Changes

*   When submitting a form from a `submitter` element, prefer the built-in `new FormData(form, submitter)` instead of the previous manual approach in modern browsers (those that support the new `submitter` parameter) ([#9865](https://github.com/remix-run/react-router/pull/9865)
    )
    *   For browsers that don't support it, we continue to just append the submit button's entry to the end, and we also add rudimentary support for `type="image"` buttons
    *   If developers want full spec-compliant support for legacy browsers, they can use the `formdata-submitter-polyfill`
*   Call `window.history.pushState/replaceState` _before_ updating React Router state (instead of after) so that `window.location` matches `useLocation` during synchronous React 17 rendering ([#10448](https://github.com/remix-run/react-router/pull/10448)
    )
    *   ⚠️ Note: generally apps should not be relying on `window.location` and should always reference `useLocation` when possible, as `window.location` will not be in sync 100% of the time (due to `popstate` events, concurrent mode, etc.)
*   Avoid calling `shouldRevalidate` for fetchers that have not yet completed a data load ([#10623](https://github.com/remix-run/react-router/pull/10623)
    )
*   Strip `basename` from the `location` provided to `<ScrollRestoration getKey>` to match the `useLocation` behavior ([#10550](https://github.com/remix-run/react-router/pull/10550)
    )
*   Strip `basename` from locations provided to `unstable_useBlocker` functions to match the `useLocation` behavior ([#10573](https://github.com/remix-run/react-router/pull/10573)
    )
*   Fix `unstable_useBlocker` key issues in `StrictMode` ([#10573](https://github.com/remix-run/react-router/pull/10573)
    )
*   Fix `generatePath` when passed a numeric `0` value parameter ([#10612](https://github.com/remix-run/react-router/pull/10612)
    )
*   Fix `tsc --skipLibCheck:false` issues on React 17 ([#10622](https://github.com/remix-run/react-router/pull/10622)
    )
*   Upgrade `typescript` to 5.1 ([#10581](https://github.com/remix-run/react-router/pull/10581)
    )

**Full Changelog**: [`v6.13.0...v6.14.0`](https://github.com/remix-run/react-router/compare/react-router@6.13.0...react-router@6.14.0)

[](#v6130)
v6.13.0
------------------

Date: 2023-06-14

### [](#whats-changed-14)
What's Changed

`6.13.0` is really a patch release in spirit but comes with a SemVer minor bump since we added a new future flag.

#### [](#futurev7_starttransition)
`future.v7_startTransition`

The **tl;dr;** is that `6.13.0` is the same as [`6.12.0`](https://github.com/remix-run/react-router/releases/tag/react-router%406.12.0)
 bue we've moved the usage of `React.startTransition` behind an opt-in `future.v7_startTransition` [future flag](https://reactrouter.com/v6/guides/api-development-strategy)
 because we found that there are applications in the wild that are currently using `Suspense` in ways that are incompatible with `React.startTransition`.

Therefore, in `6.13.0` the default behavior will no longer leverage `React.startTransition`:

    <BrowserRouter>
      <Routes>{/*...*/}</Routes>
    </BrowserRouter>
    
    <RouterProvider router={router} />
    

If you wish to enable `React.startTransition`, pass the future flag to your router component:

    <BrowserRouter future={{ v7_startTransition: true }}>
      <Routes>{/*...*/}</Routes>
    </BrowserRouter>
    
    <RouterProvider router={router} future={{ v7_startTransition: true }}/>
    

We recommend folks adopt this flag sooner rather than later to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of `React.startTransition` until v7. Issues usually boil down to creating net-new promises during the render cycle, so if you run into issues when opting into `React.startTransition`, you should either lift your promise creation out of the render cycle or put it behind a `useMemo`.

### [](#minor-changes-24)
Minor Changes

*   Move `React.startTransition` usage behinds a future flag ([#10596](https://github.com/remix-run/react-router/pull/10596)
    )

### [](#patch-changes-50)
Patch Changes

*   Work around webpack/terser `React.startTransition` minification bug in production mode ([#10588](https://github.com/remix-run/react-router/pull/10588)
    )

**Full Changelog**: [`v6.12.1...v6.13.0`](https://github.com/remix-run/react-router/compare/react-router@6.12.1...react-router@6.13.0)

[](#v6121)
v6.12.1
------------------

Date: 2023-06-08

> \[!WARNING\] Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569)
>  and [#10579](https://github.com/remix-run/react-router/issues/10579)
>  for more details.

### [](#patch-changes-51)
Patch Changes

*   Adjust feature detection of `React.startTransition` to fix webpack + react 17 compilation error ([#10569](https://github.com/remix-run/react-router/pull/10569)
    )

**Full Changelog**: [`v6.12.0...v6.12.1`](https://github.com/remix-run/react-router/compare/react-router@6.12.0...react-router@6.12.1)

[](#v6120)
v6.12.0
------------------

Date: 2023-06-06

> \[!WARNING\] Please use version `6.13.0` or later instead of `6.12.0`/`6.12.1`. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See [#10569](https://github.com/remix-run/react-router/pull/10569)
>  and [#10579](https://github.com/remix-run/react-router/issues/10579)
>  for more details.

### [](#whats-changed-15)
What's Changed

#### [](#reactstarttransition-support)
`React.startTransition` support

With `6.12.0` we've added better support for suspending components by wrapping the internal router state updates in [`React.startTransition`](https://react.dev/reference/react/startTransition)
. This means that, for example, if one of your components in a destination route suspends and you have not provided a [`Suspense`](https://react.dev/reference/react/Suspense)
 boundary to show a fallback, React will delay the rendering of the new UI and show the old UI until that asynchronous operation resolves. This could be useful for waiting for things such as waiting for images or CSS files to load (and technically, yes, you could use it for data loading but we'd still recommend using loaders for that 😀). For a quick overview of this usage, check out [Ryan's demo on Twitter](https://twitter.com/remix_run/status/1658976420767604736)
.

### [](#minor-changes-25)
Minor Changes

*   Wrap internal router state updates with `React.startTransition` ([#10438](https://github.com/remix-run/react-router/pull/10438)
    )

### [](#patch-changes-52)
Patch Changes

*   Allow fetcher revalidations to complete if submitting fetcher is deleted ([#10535](https://github.com/remix-run/react-router/pull/10535)
    )
*   Re-throw `DOMException` (`DataCloneError`) when attempting to perform a `PUSH` navigation with non-serializable state. ([#10427](https://github.com/remix-run/react-router/pull/10427)
    )
*   Ensure revalidations happen when hash is present ([#10516](https://github.com/remix-run/react-router/pull/10516)
    )
*   Upgrade `jest` and `jsdom` ([#10453](https://github.com/remix-run/react-router/pull/10453)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.6.3` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#163)
        )

**Full Changelog**: [`v6.11.2...v6.12.0`](https://github.com/remix-run/react-router/compare/react-router@6.11.2...react-router@6.12.0)

[](#v6112)
v6.11.2
------------------

Date: 2023-05-17

### [](#patch-changes-53)
Patch Changes

*   Fix `basename` duplication in descendant `<Routes>` inside a `<RouterProvider>` ([#10492](https://github.com/remix-run/react-router/pull/10492)
    )
*   Fix bug where initial data load would not kick off when hash is present ([#10493](https://github.com/remix-run/react-router/pull/10493)
    )
*   Export `SetURLSearchParams` type ([#10444](https://github.com/remix-run/react-router/pull/10444)
    )
*   Fix Remix HMR-driven error boundaries by properly reconstructing new routes and `manifest` in `_internalSetRoutes` ([#10437](https://github.com/remix-run/react-router/pull/10437)
    )

**Full Changelog**: [`v6.11.1...v6.11.2`](https://github.com/remix-run/react-router/compare/react-router@6.11.1...react-router@6.11.2)

[](#v6111)
v6.11.1
------------------

Date: 2023-05-03

### [](#patch-changes-54)
Patch Changes

*   Fix usage of `Component` API within descendant `<Routes>` ([#10434](https://github.com/remix-run/react-router/pull/10434)
    )
*   Fix bug when calling `useNavigate` from `<Routes>` inside a `<RouterProvider>` ([#10432](https://github.com/remix-run/react-router/pull/10432)
    )
*   Fix usage of `<Navigate>` in strict mode when using a data router ([#10435](https://github.com/remix-run/react-router/pull/10435)
    )
*   Fix `basename` handling when navigating without a path ([#10433](https://github.com/remix-run/react-router/pull/10433)
    )
*   "Same hash" navigations no longer re-run loaders to match browser behavior (i.e. `/path#hash -> /path#hash`) ([#10408](https://github.com/remix-run/react-router/pull/10408)
    )

**Full Changelog**: [`v6.11.0...v6.11.1`](https://github.com/remix-run/react-router/compare/react-router@6.11.0...react-router@6.11.1)

[](#v6110)
v6.11.0
------------------

Date: 2023-04-28

### [](#minor-changes-26)
Minor Changes

*   Enable `basename` support in `useFetcher` ([#10336](https://github.com/remix-run/react-router/pull/10336)
    )
    *   If you were previously working around this issue by manually prepending the `basename` then you will need to remove the manually prepended `basename` from your `fetcher` calls (`fetcher.load('/basename/route') -> fetcher.load('/route')`)
*   Updated dependencies:
    *   `@remix-run/router@1.6.0` ([Changelog](https://github.com/remix-run/react-router/blob/main/packages/router/CHANGELOG.md#160)
        )

### [](#patch-changes-55)
Patch Changes

*   When using a `RouterProvider`, `useNavigate`/`useSubmit`/`fetcher.submit` are now stable across location changes, since we can handle relative routing via the `@remix-run/router` instance and get rid of our dependence on `useLocation()` ([#10336](https://github.com/remix-run/react-router/pull/10336)
    )
    *   When using `BrowserRouter`, these hooks remain unstable across location changes because they still rely on `useLocation()`
*   Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on `action` submissions or `router.revalidate` calls ([#10344](https://github.com/remix-run/react-router/pull/10344)
    )
*   Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287)
    )
*   Fail gracefully on `<Link to="//">` and other invalid URL values ([#10367](https://github.com/remix-run/react-router/pull/10367)
    )
*   Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81)
     where router state updates got propagated _before_ other normal `useState` updates, which could lead to foot guns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377)
    , [#10409](https://github.com/remix-run/react-router/pull/10409)
    )
*   Log loader/action errors caught by the default error boundary to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286)
    )
*   Fix bug preventing rendering of descendant `<Routes>` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374)
    )
*   Fix detection of `useNavigate` in the render cycle by setting the `activeRef` in a layout effect, allowing the `navigate` function to be passed to child components and called in a `useEffect` there ([#10394](https://github.com/remix-run/react-router/pull/10394)
    )
*   Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369)
    )
*   Enhance `LoaderFunction`/`ActionFunction` return type to prevent `undefined` from being a valid return value ([#10267](https://github.com/remix-run/react-router/pull/10267)
    )
*   Ensure proper 404 error on `fetcher.load` call to a route without a `loader` ([#10345](https://github.com/remix-run/react-router/pull/10345)
    )
*   Decouple `AbortController` usage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation ([#10271](https://github.com/remix-run/react-router/pull/10271)
    )

**Full Changelog**: [`v6.10.0...v6.11.0`](https://github.com/remix-run/react-router/compare/react-router@6.10.0...react-router@6.11.0)

[](#v6100)
v6.10.0
------------------

Date: 2023-03-29

### [](#whats-changed-16)
What's Changed

We recently published a post over on the Remix Blog titled ["Future Proofing Your Remix App"](https://remix.run/blog/future-flags)
 that goes through our strategy to ensure smooth upgrades for your Remix and React Router apps going forward. React Router `6.10.0` adds support for these flags (for data routers) which you can specify when you create your router:

    const router = createBrowserRouter(routes, {
      future: {
        // specify future flags here
      },
    });
    

You can also check out the docs [here](https://reactrouter.com/en/dev/guides/api-development-strategy)
 and [here](https://reactrouter.com/en/dev/routers/create-browser-router#future)
.

### [](#minor-changes-27)
Minor Changes

#### [](#futurev7_normalizeformmethod)
`future.v7_normalizeFormMethod`

The first future flag being introduced is `future.v7_normalizeFormMethod` which will normalize the exposed `useNavigation()/useFetcher()` `formMethod` fields as uppercase HTTP methods to align with the `fetch()` (and some Remix) behavior. ([#10207](https://github.com/remix-run/react-router/pull/10207)
)

*   When `future.v7_normalizeFormMethod` is unspecified or set to `false` (default v6 behavior),
    *   `useNavigation().formMethod` is lowercase
    *   `useFetcher().formMethod` is lowercase
*   When `future.v7_normalizeFormMethod === true`:
    *   `useNavigation().formMethod` is UPPERCASE
    *   `useFetcher().formMethod` is UPPERCASE

### [](#patch-changes-56)
Patch Changes

*   Fix `createStaticHandler` to also check for `ErrorBoundary` on routes in addition to `errorElement` ([#10190](https://github.com/remix-run/react-router/pull/10190)
    )
*   Fix route ID generation when using Fragments in `createRoutesFromElements` ([#10193](https://github.com/remix-run/react-router/pull/10193)
    )
*   Provide fetcher submission to `shouldRevalidate` if the fetcher action redirects ([#10208](https://github.com/remix-run/react-router/pull/10208)
    )
*   Properly handle `lazy()` errors during router initialization ([#10201](https://github.com/remix-run/react-router/pull/10201)
    )
*   Remove `instanceof` check for `DeferredData` to be resilient to ESM/CJS boundaries in SSR bundling scenarios ([#10247](https://github.com/remix-run/react-router/pull/10247)
    )
*   Update to latest `@remix-run/web-fetch@4.3.3` ([#10216](https://github.com/remix-run/react-router/pull/10216)
    )

**Full Changelog**: [`v6.9.0...v6.10.0`](https://github.com/remix-run/react-router/compare/react-router@6.9.0...react-router@6.10.0)

[](#v690)
v6.9.0
----------------

Date: 2023-03-10

### [](#whats-changed-17)
What's Changed

#### [](#componenterrorboundary-route-properties)
`Component`/`ErrorBoundary` route properties

React Router now supports an alternative way to define your route `element` and `errorElement` fields as React Components instead of React Elements. You can instead pass a React Component to the new `Component` and `ErrorBoundary` fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do `Component`/`ErrorBoundary` will "win"

**Example JSON Syntax**

    // Both of these work the same:
    const elementRoutes = [{\
      path: '/',\
      element: <Home />,\
      errorElement: <HomeError />,\
    }]
    
    const componentRoutes = [{\
      path: '/',\
      Component: Home,\
      ErrorBoundary: HomeError,\
    }]
    
    function Home() { ... }
    function HomeError() { ... }
    

**Example JSX Syntax**

    // Both of these work the same:
    const elementRoutes = createRoutesFromElements(
      <Route path='/' element={<Home />} errorElement={<HomeError /> } />
    );
    
    const componentRoutes = createRoutesFromElements(
      <Route path='/' Component={Home} ErrorBoundary={HomeError} />
    );
    
    function Home() { ... }
    function HomeError() { ... }
    

#### [](#introducing-lazy-route-modules)
Introducing Lazy Route Modules

In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new `lazy()` route property. This is an async function that resolves the non-route-matching portions of your route definition (`loader`, `action`, `element`/`Component`, `errorElement`/`ErrorBoundary`, `shouldRevalidate`, `handle`).

Lazy routes are resolved on initial load and during the `loading` or `submitting` phase of a navigation or fetcher call. You cannot lazily define route-matching properties (`path`, `index`, `children`) since we only execute your lazy route functions after we've matched known routes.

Your `lazy` functions will typically return the result of a dynamic import.

    // In this example, we assume most folks land on the homepage so we include that
    // in our critical-path bundle, but then we lazily load modules for /a and /b so
    // they don't load until the user navigates to those routes
    let routes = createRoutesFromElements(
      <Route path="/" element={<Layout />}>
        <Route index element={<Home />} />
        <Route path="a" lazy={() => import("./a")} />
        <Route path="b" lazy={() => import("./b")} />
      </Route>
    );
    

Then in your lazy route modules, export the properties you want defined for the route:

    export async function loader({ request }) {
      let data = await fetchData(request);
      return json(data);
    }
    
    // Export a `Component` directly instead of needing to create a React Element from it
    export function Component() {
      let data = useLoaderData();
    
      return (
        <>
          <h1>You made it!</h1>
          <p>{data}</p>
        </>
      );
    }
    
    // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
    export function ErrorBoundary() {
      let error = useRouteError();
      return isRouteErrorResponse(error) ? (
        <h1>
          {error.status} {error.statusText}
        </h1>
      ) : (
        <h1>{error.message || error}</h1>
      );
    }
    

An example of this in action can be found in the [`examples/lazy-loading-router-provider`](https://github.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider)
 directory of the repository. For more info, check out the [`lazy` docs](https://reactrouter.com/v6/route/lazy)
.

🙌 Huge thanks to @rossipedia for the [Initial Proposal](https://github.com/remix-run/react-router/discussions/9826)
 and [POC Implementation](https://github.com/remix-run/react-router/pull/9830)
.

### [](#minor-changes-28)
Minor Changes

*   Add support for `route.Component`/`route.ErrorBoundary` properties ([#10045](https://github.com/remix-run/react-router/pull/10045)
    )
*   Add support for `route.lazy` ([#10045](https://github.com/remix-run/react-router/pull/10045)
    )

### [](#patch-changes-57)
Patch Changes

*   Improve memoization for context providers to avoid unnecessary re-renders ([#9983](https://github.com/remix-run/react-router/pull/9983)
    )
*   Fix `generatePath` incorrectly applying parameters in some cases ([#10078](https://github.com/remix-run/react-router/pull/10078)
    )
*   `[react-router-dom-v5-compat]` Add missed data router API re-exports ([#10171](https://github.com/remix-run/react-router/pull/10171)
    )

**Full Changelog**: [`v6.8.2...v6.9.0`](https://github.com/remix-run/react-router/compare/react-router@6.8.2...react-router@6.9.0)

[](#v682)
v6.8.2
----------------

Date: 2023-02-27

### [](#patch-changes-58)
Patch Changes

*   Treat same-origin absolute URLs in `<Link to>` as external if they are outside of the router `basename` ([#10135](https://github.com/remix-run/react-router/pull/10135)
    )
*   Correctly perform a hard redirect for same-origin absolute URLs outside of the router `basename` ([#10076](https://github.com/remix-run/react-router/pull/10076)
    )
*   Fix SSR of absolute `<Link to>` urls ([#10112](https://github.com/remix-run/react-router/pull/10112)
    )
*   Properly escape HTML characters in `StaticRouterProvider` serialized hydration data ([#10068](https://github.com/remix-run/react-router/pull/10068)
    )
*   Fix `useBlocker` to return `IDLE_BLOCKER` during SSR ([#10046](https://github.com/remix-run/react-router/pull/10046)
    )
*   Ensure status code and headers are maintained for `defer` loader responses in `createStaticHandler`'s `query()` method ([#10077](https://github.com/remix-run/react-router/pull/10077)
    )
*   Change `invariant` to an `UNSAFE_invariant` export since it's only intended for internal use ([#10066](https://github.com/remix-run/react-router/pull/10066)
    )

**Full Changelog**: [`v6.8.1...v6.8.2`](https://github.com/remix-run/react-router/compare/react-router@6.8.1...react-router@6.8.2)

[](#v681)
v6.8.1
----------------

Date: 2023-02-06

### [](#patch-changes-59)
Patch Changes

*   Remove inaccurate console warning for POP navigations and update active blocker logic ([#10030](https://github.com/remix-run/react-router/pull/10030)
    )
*   Only check for differing origin on absolute URL redirects ([#10033](https://github.com/remix-run/react-router/pull/10033)
    )
*   Improved absolute url detection in `Link` component (now also supports `mailto:` urls) ([#9994](https://github.com/remix-run/react-router/pull/9994)
    )
*   Fix partial object (search or hash only) pathnames losing current path value ([#10029](https://github.com/remix-run/react-router/pull/10029)
    )

**Full Changelog**: [`v6.8.0...v6.8.1`](https://github.com/remix-run/react-router/compare/react-router@6.8.0...react-router@6.8.1)

[](#v680)
v6.8.0
----------------

Date: 2023-01-26

### [](#minor-changes-29)
Minor Changes

Support absolute URLs in `<Link to>`. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. ([#9900](https://github.com/remix-run/react-router/pull/9900)
)

    <Link to="https://neworigin.com/some/path">    {/* Document request */}
    <Link to="//neworigin.com/some/path">          {/* Document request */}
    <Link to="https://www.currentorigin.com/path"> {/* Client-side navigation */}
    

### [](#patch-changes-60)
Patch Changes

*   Fixes 2 separate issues for revalidating fetcher `shouldRevalidate` calls ([#9948](https://github.com/remix-run/react-router/pull/9948)
    )
    *   The `shouldRevalidate` function was only being called for _explicit_ revalidation scenarios (after a mutation, manual `useRevalidator` call, or an `X-Remix-Revalidate` header used for cookie setting in Remix). It was not properly being called on _implicit_ revalidation scenarios that also apply to navigation `loader` revalidation, such as a change in search params or clicking a link for the page we're already on. It's now correctly called in those additional scenarios.
    *   The parameters being passed were incorrect and inconsistent with one another since the `current*`/`next*` parameters reflected the static `fetcher.load` URL (and thus were identical). Instead, they should have reflected the navigation that triggered the revalidation (as the `form*` parameters did). These parameters now correctly reflect the triggering navigation.
*   Fix bug with search params removal via `useSearchParams` ([#9969](https://github.com/remix-run/react-router/pull/9969)
    )
*   Respect `preventScrollReset` on `<fetcher.Form>` ([#9963](https://github.com/remix-run/react-router/pull/9963)
    )
*   Fix navigation for hash routers on manual URL changes ([#9980](https://github.com/remix-run/react-router/pull/9980)
    )
*   Use `pagehide` instead of `beforeunload` for `<ScrollRestoration>`. This has better cross-browser support, specifically on Mobile Safari. ([#9945](https://github.com/remix-run/react-router/pull/9945)
    )
*   Do not short circuit on hash change only mutation submissions ([#9944](https://github.com/remix-run/react-router/pull/9944)
    )
*   Remove `instanceof` check from `isRouteErrorResponse` to avoid bundling issues on the server ([#9930](https://github.com/remix-run/react-router/pull/9930)
    )
*   Detect when a `defer` call only contains critical data and remove the `AbortController` ([#9965](https://github.com/remix-run/react-router/pull/9965)
    )
*   Send the name as the value when url-encoding `File` `FormData` entries ([#9867](https://github.com/remix-run/react-router/pull/9867)
    )
*   `react-router-dom-v5-compat` - Fix SSR `useLayoutEffect` `console.error` when using `CompatRouter` ([#9820](https://github.com/remix-run/react-router/pull/9820)
    )

**Full Changelog**: [`v6.7.0...v6.8.0`](https://github.com/remix-run/react-router/compare/react-router@6.7.0...react-router@6.8.0)

[](#v670)
v6.7.0
----------------

Date: 2023-01-18

### [](#minor-changes-30)
Minor Changes

*   Add `unstable_useBlocker`/`unstable_usePrompt` hooks for blocking navigations within the app's location origin ([#9709](https://github.com/remix-run/react-router/pull/9709)
    , [#9932](https://github.com/remix-run/react-router/pull/9932)
    )
*   Add `preventScrollReset` prop to `<Form>` ([#9886](https://github.com/remix-run/react-router/pull/9886)
    )

### [](#patch-changes-61)
Patch Changes

*   Added pass-through event listener options argument to `useBeforeUnload` ([#9709](https://github.com/remix-run/react-router/pull/9709)
    )
*   Fix `generatePath` when optional params are present ([#9764](https://github.com/remix-run/react-router/pull/9764)
    )
*   Update `<Await>` to accept `ReactNode` as children function return result ([#9896](https://github.com/remix-run/react-router/pull/9896)
    )
*   Improved absolute redirect url detection in actions/loaders ([#9829](https://github.com/remix-run/react-router/pull/9829)
    )
*   Fix URL creation with memory histories ([#9814](https://github.com/remix-run/react-router/pull/9814)
    )
*   Fix scroll reset if a submission redirects ([#9886](https://github.com/remix-run/react-router/pull/9886)
    )
*   Fix 404 bug with same-origin absolute redirects ([#9913](https://github.com/remix-run/react-router/pull/9913)
    )
*   Streamline `jsdom` bug workaround in tests ([#9824](https://github.com/remix-run/react-router/pull/9824)
    )

**Full Changelog**: [`v6.6.2...v6.7.0`](https://github.com/remix-run/react-router/compare/react-router@6.6.2...react-router@6.7.0)

[](#v662)
v6.6.2
----------------

Date: 2023-01-09

### [](#patch-changes-62)
Patch Changes

*   Ensure `useId` consistency during SSR ([#9805](https://github.com/remix-run/react-router/pull/9805)
    )

**Full Changelog**: [`v6.6.1...v6.6.2`](https://github.com/remix-run/react-router/compare/react-router@6.6.1...react-router@6.6.2)

[](#v661)
v6.6.1
----------------

Date: 2022-12-23

### [](#patch-changes-63)
Patch Changes

*   Include submission info in `shouldRevalidate` on action redirects ([#9777](https://github.com/remix-run/react-router/pull/9777)
    , [#9782](https://github.com/remix-run/react-router/pull/9782)
    )
*   Reset `actionData` on action redirect to current location ([#9772](https://github.com/remix-run/react-router/pull/9772)
    )

**Full Changelog**: [`v6.6.0...v6.6.1`](https://github.com/remix-run/react-router/compare/react-router@6.6.0...react-router@6.6.1)

[](#v660)
v6.6.0
----------------

Date: 2022-12-21

### [](#whats-changed-18)
What's Changed

This minor release is primarily to stabilize our SSR APIs for Data Routers now that we've wired up the new `RouterProvider` in Remix as part of the [React Router-ing Remix](https://remix.run/blog/react-routering-remix)
 work.

### [](#minor-changes-31)
Minor Changes

*   Remove `unstable_` prefix from `createStaticHandler`/`createStaticRouter`/`StaticRouterProvider` ([#9738](https://github.com/remix-run/react-router/pull/9738)
    )
*   Add `useBeforeUnload()` hook ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )

### [](#patch-changes-64)
Patch Changes

*   Support uppercase `<Form method>` and `useSubmit` method values ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix `<button formmethod>` form submission overriddes ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix explicit `replace` on submissions and `PUSH` on submission to new paths ([#9734](https://github.com/remix-run/react-router/pull/9734)
    )
*   Prevent `useLoaderData` usage in `errorElement` ([#9735](https://github.com/remix-run/react-router/pull/9735)
    )
*   Proper hydration of `Error` objects from `StaticRouterProvider` ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Skip initial scroll restoration for SSR apps with `hydrationData` ([#9664](https://github.com/remix-run/react-router/pull/9664)
    )
*   Fix a few bugs where loader/action data wasn't properly cleared on errors ([#9735](https://github.com/remix-run/react-router/pull/9735)
    )

**Full Changelog**: [`v6.5.0...v6.6.0`](https://github.com/remix-run/react-router/compare/react-router@6.5.0...react-router@6.6.0)

[](#v650)
v6.5.0
----------------

Date: 2022-12-16

### [](#whats-changed-19)
What's Changed

This release introduces support for [Optional Route Segments](https://github.com/remix-run/react-router/issues/9546)
. Now, adding a `?` to the end of any path segment will make that entire segment optional. This works for both static segments and dynamic parameters.

**Optional Params Examples**

*   `<Route path=":lang?/about>` will match:
    *   `/:lang/about`
    *   `/about`
*   `<Route path="/multistep/:widget1?/widget2?/widget3?">` will match:
    *   `/multistep`
    *   `/multistep/:widget1`
    *   `/multistep/:widget1/:widget2`
    *   `/multistep/:widget1/:widget2/:widget3`

**Optional Static Segment Example**

*   `<Route path="/home?">` will match:
    *   `/`
    *   `/home`
*   `<Route path="/fr?/about">` will match:
    *   `/about`
    *   `/fr/about`

### [](#minor-changes-32)
Minor Changes

*   Allows optional routes and optional static segments ([#9650](https://github.com/remix-run/react-router/pull/9650)
    )

### [](#patch-changes-65)
Patch Changes

*   Stop incorrectly matching on partial named parameters, i.e. `<Route path="prefix-:param">`, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the `useParams` call site: ([#9506](https://github.com/remix-run/react-router/pull/9506)
    )

    // Old behavior at URL /prefix-123
    <Route path="prefix-:id" element={<Comp /> }>
    
    function Comp() {
      let params = useParams(); // { id: '123' }
      let id = params.id; // "123"
      ...
    }
    
    // New behavior at URL /prefix-123
    <Route path=":id" element={<Comp /> }>
    
    function Comp() {
      let params = useParams(); // { id: 'prefix-123' }
      let id = params.id.replace(/^prefix-/, ''); // "123"
      ...
    }
    

*   Persist `headers` on `loader` `request`'s after SSR document `action` request ([#9721](https://github.com/remix-run/react-router/pull/9721)
    )
*   Fix requests sent to revalidating loaders so they reflect a GET request ([#9660](https://github.com/remix-run/react-router/pull/9660)
    )
*   Fix issue with deeply nested optional segments ([#9727](https://github.com/remix-run/react-router/pull/9727)
    )
*   GET forms now expose a submission on the loading navigation ([#9695](https://github.com/remix-run/react-router/pull/9695)
    )
*   Fix error boundary tracking for multiple errors bubbling to the same boundary ([#9702](https://github.com/remix-run/react-router/pull/9702)
    )

**Full Changelog**: [`v6.4.5...v6.5.0`](https://github.com/remix-run/react-router/compare/react-router@6.4.5...react-router@6.5.0)

[](#v645)
v6.4.5
----------------

Date: 2022-12-07

### [](#patch-changes-66)
Patch Changes

*   Fix requests sent to revalidating loaders so they reflect a `GET` request ([#9680](https://github.com/remix-run/react-router/pull/9680)
    )
*   Remove `instanceof Response` checks in favor of `isResponse` ([#9690](https://github.com/remix-run/react-router/pull/9690)
    )
*   Fix `URL` creation in Cloudflare Pages or other non-browser-environments ([#9682](https://github.com/remix-run/react-router/pull/9682)
    , [#9689](https://github.com/remix-run/react-router/pull/9689)
    )
*   Add `requestContext` support to static handler `query`/`queryRoute` ([#9696](https://github.com/remix-run/react-router/pull/9696)
    )
    *   Note that the unstable API of `queryRoute(path, routeId)` has been changed to `queryRoute(path, { routeId, requestContext })`

**Full Changelog**: [`v6.4.4...v6.4.5`](https://github.com/remix-run/react-router/compare/react-router@6.4.4...react-router@6.4.5)

[](#v644)
v6.4.4
----------------

Date: 2022-11-30

### [](#patch-changes-67)
Patch Changes

*   Throw an error if an `action`/`loader` function returns `undefined` as revalidations need to know whether the loader has previously been executed. `undefined` also causes issues during SSR stringification for hydration. You should always ensure your `loader`/`action` returns a value, and you may return `null` if you don't wish to return anything. ([#9511](https://github.com/remix-run/react-router/pull/9511)
    )
*   Properly handle redirects to external domains ([#9590](https://github.com/remix-run/react-router/pull/9590)
    , [#9654](https://github.com/remix-run/react-router/pull/9654)
    )
*   Preserve the HTTP method on 307/308 redirects ([#9597](https://github.com/remix-run/react-router/pull/9597)
    )
*   Support `basename` in static data routers ([#9591](https://github.com/remix-run/react-router/pull/9591)
    )
*   Enhanced `ErrorResponse` bodies to contain more descriptive text in internal 403/404/405 scenarios
*   Fix issues with encoded characters in `NavLink` and descendant `<Routes>` ([#9589](https://github.com/remix-run/react-router/pull/9589)
    , [#9647](https://github.com/remix-run/react-router/pull/9647)
    )
*   Properly serialize/deserialize `ErrorResponse` instances when using built-in hydration ([#9593](https://github.com/remix-run/react-router/pull/9593)
    )
*   Support `basename` in static data routers ([#9591](https://github.com/remix-run/react-router/pull/9591)
    )
*   Updated dependencies:
    *   `@remix-run/router@1.0.4`
    *   `react-router@6.4.4`

**Full Changelog**: [`v6.4.3...v6.4.4`](https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4)

[](#v643)
v6.4.3
----------------

Date: 2022-11-01

### [](#patch-changes-68)
Patch Changes

*   Generate correct `<a href>` values when using `createHashRouter` ([#9409](https://github.com/remix-run/react-router/pull/9409)
    )
*   Better handle encoding/matching with special characters in URLs and route paths ([#9477](https://github.com/remix-run/react-router/pull/9477)
    , [#9496](https://github.com/remix-run/react-router/pull/9496)
    )
*   Generate correct `formAction` pathnames when an `index` route also has a `path` ([#9486](https://github.com/remix-run/react-router/pull/9486)
    )
*   Respect `relative=path` prop on `NavLink` ([#9453](https://github.com/remix-run/react-router/pull/9453)
    )
*   Fix `NavLink` behavior for root urls ([#9497](https://github.com/remix-run/react-router/pull/9497)
    )
*   `useRoutes` should be able to return `null` when passing `locationArg` ([#9485](https://github.com/remix-run/react-router/pull/9485)
    )
*   Fix `initialEntries` type in `createMemoryRouter` ([#9498](https://github.com/remix-run/react-router/pull/9498)
    )
*   Support `basename` and relative routing in `loader`/`action` redirects ([#9447](https://github.com/remix-run/react-router/pull/9447)
    )
*   Ignore pathless layout routes when looking for proper submission `action` function ([#9455](https://github.com/remix-run/react-router/pull/9455)
    )
*   Add UMD build for `@remix-run/router` ([#9446](https://github.com/remix-run/react-router/pull/9446)
    )
*   Fix `createURL` in local file execution in Firefox ([#9464](https://github.com/remix-run/react-router/pull/9464)
    )

**Full Changelog**: [`v6.4.2...v6.4.3`](https://github.com/remix-run/react-router/compare/react-router@6.4.2...react-router@6.4.3)

[](#v642)
v6.4.2
----------------

Date: 2022-10-06

### [](#patch-changes-69)
Patch Changes

*   Respect `basename` in `useFormAction` ([#9352](https://github.com/remix-run/react-router/pull/9352)
    )
*   Fix `IndexRouteObject` and `NonIndexRouteObject` types to make `hasErrorElement` optional ([#9394](https://github.com/remix-run/react-router/pull/9394)
    )
*   Enhance console error messages for invalid usage of data router hooks ([#9311](https://github.com/remix-run/react-router/pull/9311)
    )
*   If an index route has children, it will result in a runtime error. We have strengthened our `RouteObject`/`RouteProps` types to surface the error in TypeScript. ([#9366](https://github.com/remix-run/react-router/pull/9366)
    )

**Full Changelog**: [`v6.4.1...v6.4.2`](https://github.com/remix-run/react-router/compare/react-router@6.4.1...react-router@6.4.2)

[](#v641)
v6.4.1
----------------

Date: 2022-09-22

### [](#patch-changes-70)
Patch Changes

*   Preserve state from `initialEntries` ([#9288](https://github.com/remix-run/react-router/pull/9288)
    )
*   Preserve `?index` for fetcher get submissions to index routes ([#9312](https://github.com/remix-run/react-router/pull/9312)
    )

**Full Changelog**: [`v6.4.0...v6.4.1`](https://github.com/remix-run/react-router/compare/react-router@6.4.0...react-router@6.4.1)

[](#v640)
v6.4.0
----------------

Date: 2022-09-13

### [](#whats-changed-20)
What's Changed

#### [](#remix-data-apis)
Remix Data APIs

Whoa this is a big one! `6.4.0` brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the [docs](https://reactrouter.com/)
, especially the [feature overview](https://reactrouter.com/en/6.4.0/start/overview)
 and the [tutorial](https://reactrouter.com/en/6.4.0/start/tutorial)
.

**New `react-router` APIs**

*   Create your router with `createMemoryRouter`
*   Render your router with `<RouterProvider>`
*   Load data with a Route `loader` and mutate with a Route `action`
*   Handle errors with Route `errorElement`
*   Defer non-critical data with `defer` and `Await`

**New `react-router-dom` APIs**

*   Create your router with `createBrowserRouter`/`createHashRouter`
*   Submit data with the new `<Form>` component
*   Perform in-page data loads and mutations with `useFetcher()`
*   Defer non-critical data with `defer` and `Await`
*   Manage scroll position with `<ScrollRestoration>`
*   Perform path-relative navigations with `<Link relative="path">` ([#9160](https://github.com/remix-run/react-router/pull/9160)
    )

### [](#patch-changes-71)
Patch Changes

*   Path resolution is now trailing slash agnostic ([#8861](https://github.com/remix-run/react-router/pull/8861)
    )
*   `useLocation` returns the scoped location inside a `<Routes location>` component ([#9094](https://github.com/remix-run/react-router/pull/9094)
    )
*   Respect the `<Link replace>` prop if it is defined ([#8779](https://github.com/remix-run/react-router/pull/8779)
    )

**Full Changelog**: [`v6.3.0...v6.4.0`](https://github.com/remix-run/react-router/compare/v6.3.0...react-router%406.4.0)

[](#v630)
v6.3.0
----------------

Date: 2022-03-31

### [](#minor-changes-33)
Minor Changes

*   Added the v5 to v6 backwards compatibility package 💜 ([#8752](https://github.com/remix-run/react-router/pull/8752)
    ). The official guide can be found [in this discussion](https://github.com/remix-run/react-router/discussions/8753)
    

**Full Changelog**: [`v6.2.2...v6.3.0`](https://github.com/remix-run/react-router/compare/v6.2.2...v6.3.0)

[](#v622)
v6.2.2
----------------

Date: 2022-02-28

### [](#patch-changes-72)
Patch Changes

*   Fixed nested splat routes that begin with special URL-safe characters ([#8563](https://github.com/remix-run/react-router/pull/8563)
    )
*   Fixed a bug where index routes were missing route context in some cases ([#8497](https://github.com/remix-run/react-router/pull/8497)
    )

**Full Changelog**: [`v6.2.1...v6.2.2`](https://github.com/remix-run/react-router/compare/v6.2.1...v6.2.2)

[](#v621)
v6.2.1
----------------

Date: 2021-12-17

### [](#patch-changes-73)
Patch Changes

*   This release updates the internal `history` dependency to `5.2.0`.

**Full Changelog**: [`v6.2.0...v6.2.1`](https://github.com/remix-run/react-router/compare/v6.2.0...v6.2.1)

[](#v620)
v6.2.0
----------------

Date: 2021-12-17

### [](#minor-changes-34)
Minor Changes

*   We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts ([See the commit](https://github.com/remix-run/react-router/commit/29c7fc8b5f853b0b06ecd0f5682a9bbe6eca0715)
    ).

### [](#patch-changes-74)
Patch Changes

*   Fixed the `RouteProps` `element` type, which should be a `ReactNode` ([#8473](https://github.com/remix-run/react-router/pull/8473)
    )
*   Fixed a bug with `useOutlet` for top-level routes ([#8483](https://github.com/remix-run/react-router/pull/8483)
    )

**Full Changelog**: [`v6.1.1...v6.2.0`](https://github.com/remix-run/react-router/compare/v6.1.1...v6.2.0)

[](#v611)
v6.1.1
----------------

Date: 2021-12-11

### [](#patch-changes-75)
Patch Changes

*   In v6.1.0 we inadvertently shipped a new, undocumented API that will likely introduce bugs ([#7586](https://github.com/remix-run/react-router/pull/7586)
    ). We have flagged `HistoryRouter` as `unstable_HistoryRouter`, as this API will likely need to change before a new major release.

**Full Changelog**: [`v6.1.0...v6.1.1`](https://github.com/remix-run/react-router/compare/v6.1.0...v6.1.1)

[](#v610)
v6.1.0
----------------

Date: 2021-12-10

### [](#minor-changes-35)
Minor Changes

*   `<Outlet>` can now receive a `context` prop. This value is passed to child routes and is accessible via the new `useOutletContext` hook. See [the API docs](https://reactrouter.com/docs/en/v6/api#useoutletcontext)
     for details. ([#8461](https://github.com/remix-run/react-router/pull/8461)
    )
*   `<NavLink>` can now receive a child function for access to its props. ([#8164](https://github.com/remix-run/react-router/pull/8164)
    )
*   Improved TypeScript signature for `useMatch` and `matchPath`. For example, when you call `useMatch("foo/:bar/:baz")`, the path is parsed and the return type will be `PathMatch<"bar" | "baz">`. ([#8030](https://github.com/remix-run/react-router/pull/8030)
    )

### [](#patch-changes-76)
Patch Changes

*   Fixed a bug that broke support for base64 encoded IDs on nested routes ([#8291](https://github.com/remix-run/react-router/pull/8291)
    )
*   A few error message improvements ([#8202](https://github.com/remix-run/react-router/pull/8202)
    )

**Full Changelog**: [`v6.0.2...v6.1.0`](https://github.com/remix-run/react-router/compare/v6.0.2...v6.1.0)

[](#v602)
v6.0.2
----------------

Date: 2021-11-09

### [](#patch-changes-77)
Patch Changes

*   Added the `reloadDocument` prop to `<Link>`. This allows `<Link>` to function like a normal anchor tag by reloading the document after navigation while maintaining the relative `to` resolution ([#8283](https://github.com/remix-run/react-router/pull/8283)
    )

**Full Changelog**: [`v6.0.1...v6.0.2`](https://github.com/remix-run/react-router/compare/v6.0.1...v6.0.2)

[](#v601)
v6.0.1
----------------

Date: 2021-11-05

### [](#patch-changes-78)
Patch Changes

*   Add a default `<StaticRouter location>` value ([#8243](https://github.com/remix-run/react-router/pull/8243)
    )
*   Add invariant for using `<Route>` inside `<Routes>` to help people make the change ([#8238](https://github.com/remix-run/react-router/pull/8238)
    )

**Full Changelog**: [`v6.0.0...v6.0.1`](https://github.com/remix-run/react-router/compare/v6.0.0...v6.0.1)

[](#v600)
v6.0.0
----------------

Date: 2021-11-03

React Router v6 is here!

Please go read [our blog post for more information on all the great stuff in v6](https://remix.run/blog/react-router-v6)
 including [notes about how to upgrade from React Router v5](https://remix.run/blog/react-router-v6#upgrading-to-react-router-v6)
 and Reach Router.

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Routing v7.6.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

7.6.0

Branches

[latest (7.6.0)](/start/framework/routing)
[dev](/dev/start/framework/routing)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Routing

On this page

*   [Configuring Routes](/7.6.0/start/framework/routing#configuring-routes)
    
*   [Route Modules](/7.6.0/start/framework/routing#route-modules)
    
*   [Nested Routes](/7.6.0/start/framework/routing#nested-routes)
    
*   [Root Route](/7.6.0/start/framework/routing#root-route)
    
*   [Layout Routes](/7.6.0/start/framework/routing#layout-routes)
    
*   [Index Routes](/7.6.0/start/framework/routing#index-routes)
    
*   [Route Prefixes](/7.6.0/start/framework/routing#route-prefixes)
    
*   [Dynamic Segments](/7.6.0/start/framework/routing#dynamic-segments)
    
*   [Optional Segments](/7.6.0/start/framework/routing#optional-segments)
    
*   [Splats](/7.6.0/start/framework/routing#splats)
    
*   [Component Routes](/7.6.0/start/framework/routing#component-routes)
    

*   [Configuring Routes](/7.6.0/start/framework/routing#configuring-routes)
    
*   [Route Modules](/7.6.0/start/framework/routing#route-modules)
    
*   [Nested Routes](/7.6.0/start/framework/routing#nested-routes)
    
*   [Root Route](/7.6.0/start/framework/routing#root-route)
    
*   [Layout Routes](/7.6.0/start/framework/routing#layout-routes)
    
*   [Index Routes](/7.6.0/start/framework/routing#index-routes)
    
*   [Route Prefixes](/7.6.0/start/framework/routing#route-prefixes)
    
*   [Dynamic Segments](/7.6.0/start/framework/routing#dynamic-segments)
    
*   [Optional Segments](/7.6.0/start/framework/routing#optional-segments)
    
*   [Splats](/7.6.0/start/framework/routing#splats)
    
*   [Component Routes](/7.6.0/start/framework/routing#component-routes)
    

[](#routing)
Routing
====================

*   [Framework](../../start/modes "Available with Framework")
    
*   [Data](../../start/modes "Not available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#configuring-routes)
Configuring Routes
------------------------------------------

Routes are configured in `app/routes.ts`. Each route has two required parts: a URL pattern to match the URL, and a file path to the route module that defines its behavior.

    import {
      type RouteConfig,
      route,
    } from "@react-router/dev/routes";
    
    export default [\
      route("some/path", "./some/file.tsx"),\
      // pattern ^           ^ module file\
    ] satisfies RouteConfig;
    

Here is a larger sample route config:

    import {
      type RouteConfig,
      route,
      index,
      layout,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      index("./home.tsx"),\
      route("about", "./about.tsx"),\
    \
      layout("./auth/layout.tsx", [\
        route("login", "./auth/login.tsx"),\
        route("register", "./auth/register.tsx"),\
      ]),\
    \
      ...prefix("concerts", [\
        index("./concerts/home.tsx"),\
        route(":city", "./concerts/city.tsx"),\
        route("trending", "./concerts/trending.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

If you prefer to define your routes via file naming conventions rather than configuration, the `@react-router/fs-routes` package provides a [file system routing convention](../../how-to/file-route-conventions)
. You can even combine different routing conventions if you like:

    import {
      type RouteConfig,
      route,
    } from "@react-router/dev/routes";
    import { flatRoutes } from "@react-router/fs-routes";
    
    export default [\
      route("/", "./home.tsx"),\
    \
      ...(await flatRoutes()),\
    ] satisfies RouteConfig;
    

[](#route-modules)
Route Modules
--------------------------------

The files referenced in `routes.ts` define each route's behavior:

    route("teams/:teamId", "./team.tsx"),
    //           route module ^^^^^^^^
    

Here's a sample route module:

    // provides type safety/inference
    import type { Route } from "./+types/team";
    
    // provides `loaderData` to the component
    export async function loader({ params }: Route.LoaderArgs) {
      let team = await fetchTeam(params.teamId);
      return { name: team.name };
    }
    
    // renders after the loader is done
    export default function Component({
      loaderData,
    }: Route.ComponentProps) {
      return <h1>{loaderData.name}</h1>;
    }
    

Route modules have more features like actions, headers, and error boundaries, but they will be covered in the next guide: [Route Modules](./route-module)

[](#nested-routes)
Nested Routes
--------------------------------

Routes can be nested inside parent routes.

    import {
      type RouteConfig,
      route,
      index,
    } from "@react-router/dev/routes";
    
    export default [\
      // parent route\
      route("dashboard", "./dashboard.tsx", [\
        // child routes\
        index("./home.tsx"),\
        route("settings", "./settings.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

The path of the parent is automatically included in the child, so this config creates both `"/dashboard"` and `"/dashboard/settings"` URLs.

Child routes are rendered through the `<Outlet/>` in the parent route.

    import { Outlet } from "react-router";
    
    export default function Dashboard() {
      return (
        <div>
          <h1>Dashboard</h1>
          {/* will either be home.tsx or settings.tsx */}
          <Outlet />
        </div>
      );
    }
    

[](#root-route)
Root Route
--------------------------

Every route in `routes.ts` is nested inside the special `app/root.tsx` module.

[](#layout-routes)
Layout Routes
--------------------------------

Using `layout`, layout routes create new nesting for their children, but they don't add any segments to the URL. It's like the root route but they can be added at any level.

    import {
      type RouteConfig,
      route,
      layout,
      index,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      layout("./marketing/layout.tsx", [\
        index("./marketing/home.tsx"),\
        route("contact", "./marketing/contact.tsx"),\
      ]),\
      ...prefix("projects", [\
        index("./projects/home.tsx"),\
        layout("./projects/project-layout.tsx", [\
          route(":pid", "./projects/project.tsx"),\
          route(":pid/edit", "./projects/edit-project.tsx"),\
        ]),\
      ]),\
    ] satisfies RouteConfig;
    

Note that:

*   `home.tsx` and `contact.tsx` will be rendered into the `marketing/layout.tsx` outlet without creating any new URL paths
*   `project.tsx` and `edit-project.tsx` will be rendered into the `projects/project-layout.tsx` outlet at `/projects/:pid` and `/projects/:pid/edit` while `projects/home.tsx` will not.

[](#index-routes)
Index Routes
------------------------------

    index(componentFile),
    

Index routes render into their parent's [Outlet](https://api.reactrouter.com/v7/functions/react_router.Outlet.html)
 at their parent's URL (like a default child route).

    import {
      type RouteConfig,
      route,
      index,
    } from "@react-router/dev/routes";
    
    export default [\
      // renders into the root.tsx Outlet at /\
      index("./home.tsx"),\
      route("dashboard", "./dashboard.tsx", [\
        // renders into the dashboard.tsx Outlet at /dashboard\
        index("./dashboard-home.tsx"),\
        route("settings", "./dashboard-settings.tsx"),\
      ]),\
    ] satisfies RouteConfig;
    

Note that index routes can't have children.

[](#route-prefixes)
Route Prefixes
----------------------------------

Using `prefix`, you can add a path prefix to a set of routes without needing to introduce a parent route file.

    import {
      type RouteConfig,
      route,
      layout,
      index,
      prefix,
    } from "@react-router/dev/routes";
    
    export default [\
      layout("./marketing/layout.tsx", [\
        index("./marketing/home.tsx"),\
        route("contact", "./marketing/contact.tsx"),\
      ]),\
      ...prefix("projects", [\
        index("./projects/home.tsx"),\
        layout("./projects/project-layout.tsx", [\
          route(":pid", "./projects/project.tsx"),\
          route(":pid/edit", "./projects/edit-project.tsx"),\
        ]),\
      ]),\
    ] satisfies RouteConfig;
    

[](#dynamic-segments)
Dynamic Segments
--------------------------------------

If a path segment starts with `:` then it becomes a "dynamic segment". When the route matches the URL, the dynamic segment will be parsed from the URL and provided as `params` to other router APIs.

    route("teams/:teamId", "./team.tsx"),
    

    import type { Route } from "./+types/team";
    
    export async function loader({ params }: Route.LoaderArgs) {
      //                           ^? { teamId: string }
    }
    
    export default function Component({
      params,
    }: Route.ComponentProps) {
      params.teamId;
      //        ^ string
    }
    

You can have multiple dynamic segments in one route path:

    route("c/:categoryId/p/:productId", "./product.tsx"),
    

    import type { Route } from "./+types/product";
    
    async function loader({ params }: LoaderArgs) {
      //                    ^? { categoryId: string; productId: string }
    }
    

[](#optional-segments)
Optional Segments
----------------------------------------

You can make a route segment optional by adding a `?` to the end of the segment.

    route(":lang?/categories", "./categories.tsx"),
    

You can have optional static segments, too:

    route("users/:userId/edit?", "./user.tsx");
    

[](#splats)
Splats
------------------

Also known as "catchall" and "star" segments. If a route path pattern ends with `/*` then it will match any characters following the `/`, including other `/` characters.

    route("files/*", "./files.tsx"),
    

    export async function loader({ params }: Route.LoaderArgs) {
      // params["*"] will contain the remaining URL after files/
    }
    

You can destructure the `*`, you just have to assign it a new name. A common name is `splat`:

    const { "*": splat } = params;
    

[](#component-routes)
Component Routes
--------------------------------------

You can also use components that match the URL to elements anywhere in the component tree:

    import { Routes, Route } from "react-router";
    
    function Wizard() {
      return (
        <div>
          <h1>Some Wizard with Steps</h1>
          <Routes>
            <Route index element={<StepOne />} />
            <Route path="step-2" element={<StepTwo />} />
            <Route path="step-3" element={<StepThree />} />
          </Routes>
        </div>
      );
    }
    

Note that these routes do not participate in data loading, actions, code splitting, or any other route module features, so their use cases are more limited than those of the route module.

* * *

Next: [Route Module](./route-module)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Tutorial v6.30.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

6.30.0

Branches

[latest (7.6.0)](/home)
[dev](/dev/)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Tutorial

On this page

*   [Setup](/6.30.0/start/tutorial#setup)
    
*   [Adding a Router](/6.30.0/start/tutorial#adding-a-router)
    
*   [The Root Route](/6.30.0/start/tutorial#the-root-route)
    
*   [Handling Not Found Errors](/6.30.0/start/tutorial#handling-not-found-errors)
    
*   [The Contact Route UI](/6.30.0/start/tutorial#the-contact-route-ui)
    
*   [Nested Routes](/6.30.0/start/tutorial#nested-routes)
    
*   [Client Side Routing](/6.30.0/start/tutorial#client-side-routing)
    
*   [Loading Data](/6.30.0/start/tutorial#loading-data)
    
*   [Data Writes + HTML Forms](/6.30.0/start/tutorial#data-writes--html-forms)
    
*   [Creating Contacts](/6.30.0/start/tutorial#creating-contacts)
    
*   [URL Params in Loaders](/6.30.0/start/tutorial#url-params-in-loaders)
    
*   [Updating Data](/6.30.0/start/tutorial#updating-data)
    
*   [Updating Contacts with FormData](/6.30.0/start/tutorial#updating-contacts-with-formdata)
    
*   [Mutation Discussion](/6.30.0/start/tutorial#mutation-discussion)
    
*   [Redirecting new records to the edit page](/6.30.0/start/tutorial#redirecting-new-records-to-the-edit-page)
    
*   [Active Link Styling](/6.30.0/start/tutorial#active-link-styling)
    
*   [Global Pending UI](/6.30.0/start/tutorial#global-pending-ui)
    
*   [Deleting Records](/6.30.0/start/tutorial#deleting-records)
    
*   [Contextual Errors](/6.30.0/start/tutorial#contextual-errors)
    
*   [Index Routes](/6.30.0/start/tutorial#index-routes)
    
*   [Cancel Button](/6.30.0/start/tutorial#cancel-button)
    
*   [URL Search Params and GET Submissions](/6.30.0/start/tutorial#url-search-params-and-get-submissions)
    
*   [GET Submissions with Client Side Routing](/6.30.0/start/tutorial#get-submissions-with-client-side-routing)
    
*   [Synchronizing URLs to Form State](/6.30.0/start/tutorial#synchronizing-urls-to-form-state)
    
*   [Submitting Forms `onChange`](/6.30.0/start/tutorial#submitting-forms-onchange)
    
*   [Adding Search Spinner](/6.30.0/start/tutorial#adding-search-spinner)
    
*   [Managing the History Stack](/6.30.0/start/tutorial#managing-the-history-stack)
    
*   [Mutations Without Navigation](/6.30.0/start/tutorial#mutations-without-navigation)
    
*   [Optimistic UI](/6.30.0/start/tutorial#optimistic-ui)
    
*   [Not Found Data](/6.30.0/start/tutorial#not-found-data)
    
*   [Pathless Routes](/6.30.0/start/tutorial#pathless-routes)
    
*   [JSX Routes](/6.30.0/start/tutorial#jsx-routes)
    

*   [Setup](/6.30.0/start/tutorial#setup)
    
*   [Adding a Router](/6.30.0/start/tutorial#adding-a-router)
    
*   [The Root Route](/6.30.0/start/tutorial#the-root-route)
    
*   [Handling Not Found Errors](/6.30.0/start/tutorial#handling-not-found-errors)
    
*   [The Contact Route UI](/6.30.0/start/tutorial#the-contact-route-ui)
    
*   [Nested Routes](/6.30.0/start/tutorial#nested-routes)
    
*   [Client Side Routing](/6.30.0/start/tutorial#client-side-routing)
    
*   [Loading Data](/6.30.0/start/tutorial#loading-data)
    
*   [Data Writes + HTML Forms](/6.30.0/start/tutorial#data-writes--html-forms)
    
*   [Creating Contacts](/6.30.0/start/tutorial#creating-contacts)
    
*   [URL Params in Loaders](/6.30.0/start/tutorial#url-params-in-loaders)
    
*   [Updating Data](/6.30.0/start/tutorial#updating-data)
    
*   [Updating Contacts with FormData](/6.30.0/start/tutorial#updating-contacts-with-formdata)
    
*   [Mutation Discussion](/6.30.0/start/tutorial#mutation-discussion)
    
*   [Redirecting new records to the edit page](/6.30.0/start/tutorial#redirecting-new-records-to-the-edit-page)
    
*   [Active Link Styling](/6.30.0/start/tutorial#active-link-styling)
    
*   [Global Pending UI](/6.30.0/start/tutorial#global-pending-ui)
    
*   [Deleting Records](/6.30.0/start/tutorial#deleting-records)
    
*   [Contextual Errors](/6.30.0/start/tutorial#contextual-errors)
    
*   [Index Routes](/6.30.0/start/tutorial#index-routes)
    
*   [Cancel Button](/6.30.0/start/tutorial#cancel-button)
    
*   [URL Search Params and GET Submissions](/6.30.0/start/tutorial#url-search-params-and-get-submissions)
    
*   [GET Submissions with Client Side Routing](/6.30.0/start/tutorial#get-submissions-with-client-side-routing)
    
*   [Synchronizing URLs to Form State](/6.30.0/start/tutorial#synchronizing-urls-to-form-state)
    
*   [Submitting Forms `onChange`](/6.30.0/start/tutorial#submitting-forms-onchange)
    
*   [Adding Search Spinner](/6.30.0/start/tutorial#adding-search-spinner)
    
*   [Managing the History Stack](/6.30.0/start/tutorial#managing-the-history-stack)
    
*   [Mutations Without Navigation](/6.30.0/start/tutorial#mutations-without-navigation)
    
*   [Optimistic UI](/6.30.0/start/tutorial#optimistic-ui)
    
*   [Not Found Data](/6.30.0/start/tutorial#not-found-data)
    
*   [Pathless Routes](/6.30.0/start/tutorial#pathless-routes)
    
*   [JSX Routes](/6.30.0/start/tutorial#jsx-routes)
    

[](#tutorial)
Tutorial
======================

Welcome to the tutorial! We'll be building a small, but feature-rich app that lets you keep track of your contacts. We expect it to take between 30-60m if you're following along.

![](/_docs/tutorial/15.webp)

👉 **Every time you see this it means you need to do something in the app!**

The rest is just there for your information and deeper understanding. Let's get to it.

[](#setup)
Setup
----------------

If you're not going to follow along in your own app, you can skip this section

We'll be using [Vite](https://vitejs.dev/guide/)
 for our bundler and dev server for this tutorial. You'll need [Node.js](https://nodejs.org)
 installed for the `npm` command line tool.

👉️ **Open up your terminal and bootstrap a new React app with Vite:**

    npm create vite@latest name-of-your-project -- --template react
    # follow prompts
    cd <your new project directory>
    npm install react-router-dom # always need this!
    npm install localforage match-sorter sort-by # only for this tutorial.
    npm run dev
    

You should be able to visit the URL printed in the terminal:

     VITE v3.0.7  ready in 175 ms
    
      ➜  Local:   http://127.0.0.1:5173/
      ➜  Network: use --host to expose
    

We've got some pre-written CSS for this tutorial so we can stay focused on React Router. Feel free to judge it harshly or write your own 😅 (We did things we normally wouldn't in CSS so that the markup in this tutorial could stay as minimal as possible.)

👉 **Copy/Paste the tutorial CSS [found here](https://gist.githubusercontent.com/ryanflorence/ba20d473ef59e1965543fa013ae4163f/raw/499707f25a5690d490c7b3d54c65c65eb895930c/react-router-6.4-tutorial-css.css)
 into `src/index.css`**

This tutorial will be creating, reading, searching, updating, and deleting data. A typical web app would probably be talking to an API on your web server, but we're going to use browser storage and fake some network latency to keep this focused. None of this code is relevant to React Router, so just go ahead and copy/paste it all.

👉 **Copy/Paste the tutorial data module [found here](https://gist.githubusercontent.com/ryanflorence/1e7f5d3344c0db4a8394292c157cd305/raw/f7ff21e9ae7ffd55bfaaaf320e09c6a08a8a6611/contacts.js)
 into `src/contacts.js`**

All you need in the src folder are `contacts.js`, `main.jsx`, and `index.css`. You can delete anything else (like `App.js` and `assets`, etc.).

👉 **Delete unused files in `src/` so all you have left are these:**

    src
    ├── contacts.js
    ├── index.css
    └── main.jsx
    

If your app is running, it might blow up momentarily, just keep going 😋. And with that, we're ready to get started!

[](#adding-a-router)
Adding a Router
------------------------------------

First thing to do is create a [Browser Router](../routers/create-browser-router)
 and configure our first route. This will enable client side routing for our web app.

The `main.jsx` file is the entry point. Open it up and we'll put React Router on the page.

👉 **Create and render a [browser router](../routers/create-browser-router)
 in `main.jsx`**

    import * as React from "react";
    import * as ReactDOM from "react-dom/client";
    import {
      createBrowserRouter,
      RouterProvider,
    } from "react-router-dom";
    import "./index.css";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <div>Hello world!</div>,\
      },\
    ]);
    
    ReactDOM.createRoot(document.getElementById("root")).render(
      <React.StrictMode>
        <RouterProvider router={router} />
      </React.StrictMode>
    );
    

This first route is what we often call the "root route" since the rest of our routes will render inside of it. It will serve as the root layout of the UI, we'll have nested layouts as we get farther along.

[](#the-root-route)
The Root Route
----------------------------------

Let's add the global layout for this app.

👉 **Create `src/routes` and `src/routes/root.jsx`**

    mkdir src/routes
    touch src/routes/root.jsx
    

(If you don't want to be a command line nerd, use your editor instead of those commands 🤓)

👉 **Create the root layout component**

    export default function Root() {
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <form id="search-form" role="search">
                <input
                  id="q"
                  aria-label="Search contacts"
                  placeholder="Search"
                  type="search"
                  name="q"
                />
                <div
                  id="search-spinner"
                  aria-hidden
                  hidden={true}
                />
                <div
                  className="sr-only"
                  aria-live="polite"
                ></div>
              </form>
              <form method="post">
                <button type="submit">New</button>
              </form>
            </div>
            <nav>
              <ul>
                <li>
                  <a href={`/contacts/1`}>Your Name</a>
                </li>
                <li>
                  <a href={`/contacts/2`}>Your Friend</a>
                </li>
              </ul>
            </nav>
          </div>
          <div id="detail"></div>
        </>
      );
    }
    

Nothing React Router specific yet, so feel free to copy/paste all of that.

👉 **Set `<Root>` as the root route's [`element`](../route/route#element)
**

    /* existing imports */
    import Root from "./routes/root";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
      },\
    ]);
    
    ReactDOM.createRoot(document.getElementById("root")).render(
      <React.StrictMode>
        <RouterProvider router={router} />
      </React.StrictMode>
    );
    

The app should look something like this now. It sure is nice having a designer who can also write the CSS, isn't it? (Thank you [Jim](https://blog.jim-nielsen.com/)
 🙏).

![](/_docs/tutorial/01.webp)

[](#handling-not-found-errors)
Handling Not Found Errors
--------------------------------------------------------

It's always a good idea to know how your app responds to errors early in the project because we all write far more bugs than features when building a new app! Not only will your users get a good experience when this happens, but it helps you during development as well.

We added some links to this app, let's see what happens when we click them?

👉 **Click one of the sidebar names**

![screenshot of default React Router error element](/_docs/tutorial/02.webp)

Gross! This is the default error screen in React Router, made worse by our flex box styles on the root element in this app 😂.

Anytime your app throws an error while rendering, loading data, or performing data mutations, React Router will catch it and render an error screen. Let's make our own error page.

👉 **Create an error page component**

    touch src/error-page.jsx
    

    import { useRouteError } from "react-router-dom";
    
    export default function ErrorPage() {
      const error = useRouteError();
      console.error(error);
    
      return (
        <div id="error-page">
          <h1>Oops!</h1>
          <p>Sorry, an unexpected error has occurred.</p>
          <p>
            <i>{error.statusText || error.message}</i>
          </p>
        </div>
      );
    }
    

👉 **Set the `<ErrorPage>` as the [`errorElement`](../route/error-element)
 on the root route**

    /* previous imports */
    import ErrorPage from "./error-page";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
      },\
    ]);
    
    ReactDOM.createRoot(document.getElementById("root")).render(
      <React.StrictMode>
        <RouterProvider router={router} />
      </React.StrictMode>
    );
    

The error page should now look like this:

![new error page, but still ugly](/_docs/tutorial/03.webp)

(Well, that's not much better. Maybe somebody forgot to ask the designer to make an error page. Maybe everybody forgets to ask the designer to make an error page and then blames the designer for not thinking of it 😆)

Note that [`useRouteError`](../hooks/use-route-error)
 provides the error that was thrown. When the user navigates to routes that don't exist you'll get an [error response](../utils/is-route-error-response)
 with a "Not Found" `statusText`. We'll see some other errors later in the tutorial and discuss them more.

For now, it's enough to know that pretty much all of your errors will now be handled by this page instead of infinite spinners, unresponsive pages, or blank screens 🙌

[](#the-contact-route-ui)
The Contact Route UI
----------------------------------------------

Instead of a 404 "Not Found" page, we want to actually render something at the URLs we've linked to. For that, we need to make a new route.

👉 **Create the contact route module**

    touch src/routes/contact.jsx
    

👉 **Add the contact component UI**

It's just a bunch of elements, feel free to copy/paste.

    import { Form } from "react-router-dom";
    
    export default function Contact() {
      const contact = {
        first: "Your",
        last: "Name",
        avatar: "https://robohash.org/you.png?size=200x200",
        twitter: "your_handle",
        notes: "Some notes",
        favorite: true,
      };
    
      return (
        <div id="contact">
          <div>
            <img
              key={contact.avatar}
              src={
                contact.avatar ||
                `https://robohash.org/${contact.id}.png?size=200x200`
              }
            />
          </div>
    
          <div>
            <h1>
              {contact.first || contact.last ? (
                <>
                  {contact.first} {contact.last}
                </>
              ) : (
                <i>No Name</i>
              )}{" "}
              <Favorite contact={contact} />
            </h1>
    
            {contact.twitter && (
              <p>
                <a
                  target="_blank"
                  href={`https://twitter.com/${contact.twitter}`}
                >
                  {contact.twitter}
                </a>
              </p>
            )}
    
            {contact.notes && <p>{contact.notes}</p>}
    
            <div>
              <Form action="edit">
                <button type="submit">Edit</button>
              </Form>
              <Form
                method="post"
                action="destroy"
                onSubmit={(event) => {
                  if (
                    !confirm(
                      "Please confirm you want to delete this record."
                    )
                  ) {
                    event.preventDefault();
                  }
                }}
              >
                <button type="submit">Delete</button>
              </Form>
            </div>
          </div>
        </div>
      );
    }
    
    function Favorite({ contact }) {
      const favorite = contact.favorite;
      return (
        <Form method="post">
          <button
            name="favorite"
            value={favorite ? "false" : "true"}
            aria-label={
              favorite
                ? "Remove from favorites"
                : "Add to favorites"
            }
          >
            {favorite ? "★" : "☆"}
          </button>
        </Form>
      );
    }
    

Now that we've got a component, let's hook it up to a new route.

👉 **Import the contact component and create a new route**

    /* existing imports */
    import Contact from "./routes/contact";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
      },\
      {\
        path: "contacts/:contactId",\
        element: <Contact />,\
      },\
    ]);
    
    /* existing code */
    

Now if we click one of the links or visit `/contacts/1` we get our new component!

![contact route rendering without the parent layout](/_docs/tutorial/04.webp)

However, it's not inside of our root layout 😠

[](#nested-routes)
Nested Routes
--------------------------------

We want the contact component to render _inside_ of the `<Root>` layout like this.

![](/_docs/tutorial/05.webp)

We do it by making the contact route a _child_ of the root route.

👉 **Move the contacts route to be a child of the root route**

    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
          },\
        ],\
      },\
    ]);
    

You'll now see the root layout again but a blank page on the right. We need to tell the root route _where_ we want it to render its child routes. We do that with [`<Outlet>`](../components/outlet)
.

Find the `<div id="detail">` and put an outlet inside

👉 **Render an [`<Outlet>`](../components/outlet)
**

    import { Outlet } from "react-router-dom";
    
    export default function Root() {
      return (
        <>
          {/* all the other elements */}
          <div id="detail">
            <Outlet />
          </div>
        </>
      );
    }
    

[](#client-side-routing)
Client Side Routing
--------------------------------------------

You may or may not have noticed, but when we click the links in the sidebar, the browser is doing a full document request for the next URL instead of using React Router.

Client side routing allows our app to update the URL without requesting another document from the server. Instead, the app can immediately render new UI. Let's make it happen with [`<Link>`](../components/link)
.

👉 **Change the sidebar `<a href>` to `<Link to>`**

    import { Outlet, Link } from "react-router-dom";
    
    export default function Root() {
      return (
        <>
          <div id="sidebar">
            {/* other elements */}
    
            <nav>
              <ul>
                <li>
                  <Link to={`contacts/1`}>Your Name</Link>
                </li>
                <li>
                  <Link to={`contacts/2`}>Your Friend</Link>
                </li>
              </ul>
            </nav>
    
            {/* other elements */}
          </div>
        </>
      );
    }
    

You can open the network tab in the browser devtools to see that it's not requesting documents anymore.

[](#loading-data)
Loading Data
------------------------------

URL segments, layouts, and data are more often than not coupled (tripled?) together. We can see it in this app already:

| URL Segment | Component | Data |
| --- | --- | --- |
| /   | `<Root>` | list of contacts |
| contacts/:id | `<Contact>` | individual contact |

Because of this natural coupling, React Router has data conventions to get data into your route components easily.

There are two APIs we'll be using to load data, [`loader`](../route/loader)
 and [`useLoaderData`](../hooks/use-loader-data)
. First we'll create and export a loader function in the root module, then we'll hook it up to the route. Finally, we'll access and render the data.

👉 **Export a loader from `root.jsx`**

    import { Outlet, Link } from "react-router-dom";
    import { getContacts } from "../contacts";
    
    export async function loader() {
      const contacts = await getContacts();
      return { contacts };
    }
    

👉 **Configure the loader on the route**

    /* other imports */
    import Root, { loader as rootLoader } from "./routes/root";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
          },\
        ],\
      },\
    ]);
    

👉 **Access and render the data**

    import {
      Outlet,
      Link,
      useLoaderData,
    } from "react-router-dom";
    import { getContacts } from "../contacts";
    
    /* other code */
    
    export default function Root() {
      const { contacts } = useLoaderData();
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            {/* other code */}
    
            <nav>
              {contacts.length ? (
                <ul>
                  {contacts.map((contact) => (
                    <li key={contact.id}>
                      <Link to={`contacts/${contact.id}`}>
                        {contact.first || contact.last ? (
                          <>
                            {contact.first} {contact.last}
                          </>
                        ) : (
                          <i>No Name</i>
                        )}{" "}
                        {contact.favorite && <span>★</span>}
                      </Link>
                    </li>
                  ))}
                </ul>
              ) : (
                <p>
                  <i>No contacts</i>
                </p>
              )}
            </nav>
    
            {/* other code */}
          </div>
        </>
      );
    }
    

That's it! React Router will now automatically keep that data in sync with your UI. We don't have any data yet, so you're probably getting a blank list like this:

![](/_docs/tutorial/06.webp)

[](#data-writes--html-forms)
Data Writes + HTML Forms
-----------------------------------------------------

We'll create our first contact in a second, but first let's talk about HTML.

React Router emulates HTML Form navigation as the data mutation primitive, according to web development before the JavaScript cambrian explosion. It gives you the UX capabilities of client rendered apps with the simplicity of the "old school" web model.

While unfamiliar to some web developers, HTML forms actually cause a navigation in the browser, just like clicking a link. The only difference is in the request: links can only change the URL while forms can also change the request method (GET vs POST) and the request body (POST form data).

Without client side routing, the browser will serialize the form's data automatically and send it to the server as the request body for POST, and as URLSearchParams for GET. React Router does the same thing, except instead of sending the request to the server, it uses client side routing and sends it to a route [`action`](../route/action)
.

We can test this out by clicking the "New" button in our app. The app should blow up because the Vite server isn't configured to handle a POST request (it sends a 404, though it should probably be a 405 🤷).

![](/_docs/tutorial/07.webp)

Instead of sending that POST to the Vite server to create a new contact, let's use client side routing instead.

[](#creating-contacts)
Creating Contacts
----------------------------------------

We'll create new contacts by exporting an `action` in our root route, wiring it up to the route config, and changing our `<form>` to a React Router [`<Form>`](../components/form)
.

👉 **Create the action and change `<form>` to `<Form>`**

    import {
      Outlet,
      Link,
      useLoaderData,
      Form,
    } from "react-router-dom";
    import { getContacts, createContact } from "../contacts";
    
    export async function action() {
      const contact = await createContact();
      return { contact };
    }
    
    /* other code */
    
    export default function Root() {
      const { contacts } = useLoaderData();
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              {/* other code */}
              <Form method="post">
                <button type="submit">New</button>
              </Form>
            </div>
    
            {/* other code */}
          </div>
        </>
      );
    }
    

👉 **Import and set the action on the route**

    /* other imports */
    
    import Root, {
      loader as rootLoader,
      action as rootAction,
    } from "./routes/root";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
          },\
        ],\
      },\
    ]);
    

That's it! Go ahead and click the "New" button and you should see a new record pop into the list 🥳

![](/_docs/tutorial/08.webp)

The `createContact` method just creates an empty contact with no name or data or anything. But it does still create a record, promise!

> 🧐 Wait a sec ... How did the sidebar update? Where did we call the `action`? Where's the code to refetch the data? Where are `useState`, `onSubmit` and `useEffect`?!

This is where the "old school web" programming model shows up. As we discussed earlier, [`<Form>`](../components/form)
 prevents the browser from sending the request to the server and sends it to your route `action` instead. In web semantics, a POST usually means some data is changing. By convention, React Router uses this as a hint to automatically revalidate the data on the page after the action finishes. That means all of your `useLoaderData` hooks update and the UI stays in sync with your data automatically! Pretty cool.

[](#url-params-in-loaders)
URL Params in Loaders
------------------------------------------------

👉 **Click on the No Name record**

We should be seeing our old static contact page again, with one difference: the URL now has a real ID for the record.

![](/_docs/tutorial/09.webp)

Reviewing the route config, the route looks like this:

    [\
      {\
        path: "contacts/:contactId",\
        element: <Contact />,\
      },\
    ];
    

Note the `:contactId` URL segment. The colon (`:`) has special meaning, turning it into a "dynamic segment". Dynamic segments will match dynamic (changing) values in that position of the URL, like the contact ID. We call these values in the URL "URL Params", or just "params" for short.

These [`params`](../route/loader#params)
 are passed to the loader with keys that match the dynamic segment. For example, our segment is named `:contactId` so the value will be passed as `params.contactId`.

These params are most often used to find a record by ID. Let's try it out.

👉 **Add a loader to the contact page and access data with `useLoaderData`**

    import { Form, useLoaderData } from "react-router-dom";
    import { getContact } from "../contacts";
    
    export async function loader({ params }) {
      const contact = await getContact(params.contactId);
      return { contact };
    }
    
    export default function Contact() {
      const { contact } = useLoaderData();
      // existing code
    }
    

👉 **Configure the loader on the route**

    /* existing code */
    import Contact, {
      loader as contactLoader,
    } from "./routes/contact";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
            loader: contactLoader,\
          },\
        ],\
      },\
    ]);
    
    /* existing code */
    

![](/_docs/tutorial/10.webp)

[](#updating-data)
Updating Data
--------------------------------

Just like creating data, you update data with [`<Form>`](../components/form)
. Let's make a new route at `contacts/:contactId/edit`. Again, we'll start with the component and then wire it up to the route config.

👉 **Create the edit component**

    touch src/routes/edit.jsx
    

👉 **Add the edit page UI**

Nothing we haven't seen before, feel free to copy/paste:

    import { Form, useLoaderData } from "react-router-dom";
    
    export default function EditContact() {
      const { contact } = useLoaderData();
    
      return (
        <Form method="post" id="contact-form">
          <p>
            <span>Name</span>
            <input
              placeholder="First"
              aria-label="First name"
              type="text"
              name="first"
              defaultValue={contact?.first}
            />
            <input
              placeholder="Last"
              aria-label="Last name"
              type="text"
              name="last"
              defaultValue={contact?.last}
            />
          </p>
          <label>
            <span>Twitter</span>
            <input
              type="text"
              name="twitter"
              placeholder="@jack"
              defaultValue={contact?.twitter}
            />
          </label>
          <label>
            <span>Avatar URL</span>
            <input
              placeholder="https://example.com/avatar.jpg"
              aria-label="Avatar URL"
              type="text"
              name="avatar"
              defaultValue={contact?.avatar}
            />
          </label>
          <label>
            <span>Notes</span>
            <textarea
              name="notes"
              defaultValue={contact?.notes}
              rows={6}
            />
          </label>
          <p>
            <button type="submit">Save</button>
            <button type="button">Cancel</button>
          </p>
        </Form>
      );
    }
    

👉 **Add the new edit route**

    /* existing code */
    import EditContact from "./routes/edit";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
            loader: contactLoader,\
          },\
          {\
            path: "contacts/:contactId/edit",\
            element: <EditContact />,\
            loader: contactLoader,\
          },\
        ],\
      },\
    ]);
    
    /* existing code */
    

We want it to be rendered in the root route's outlet, so we made it a sibling to the existing child route.

(You might note we reused the `contactLoader` for this route. This is only because we're being lazy in the tutorial. There is no reason to attempt to share loaders among routes, they usually have their own.)

Alright, clicking the "Edit" button gives us this new UI:

![](/_docs/tutorial/11.webp)

[](#updating-contacts-with-formdata)
Updating Contacts with FormData
--------------------------------------------------------------------

The edit route we just created already renders a form. All we need to do to update the record is wire up an action to the route. The form will post to the action and the data will be automatically revalidated.

👉 **Add an action to the edit module**

    import {
      Form,
      useLoaderData,
      redirect,
    } from "react-router-dom";
    import { updateContact } from "../contacts";
    
    export async function action({ request, params }) {
      const formData = await request.formData();
      const updates = Object.fromEntries(formData);
      await updateContact(params.contactId, updates);
      return redirect(`/contacts/${params.contactId}`);
    }
    
    /* existing code */
    

👉 **Wire the action up to the route**

    /* existing code */
    import EditContact, {
      action as editAction,
    } from "./routes/edit";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
            loader: contactLoader,\
          },\
          {\
            path: "contacts/:contactId/edit",\
            element: <EditContact />,\
            loader: contactLoader,\
            action: editAction,\
          },\
        ],\
      },\
    ]);
    
    /* existing code */
    

Fill out the form, hit save, and you should see something like this! (Except easier on the eyes and maybe less hairy.)

![](/_docs/tutorial/12.webp)

[](#mutation-discussion)
Mutation Discussion
--------------------------------------------

> 😑 It worked, but I have no idea what is going on here...

Let's dig in a bit...

Open up `src/routes/edit.jsx` and look at the form elements. Notice how they each have a name:

    <input
      placeholder="First"
      aria-label="First name"
      type="text"
      name="first"
      defaultValue={contact.first}
    />
    

Without JavaScript, when a form is submitted, the browser will create [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData)
 and set it as the body of the request when it sends it to the server. As mentioned before, React Router prevents that and sends the request to your action instead, including the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData)
.

Each field in the form is accessible with `formData.get(name)`. For example, given the input field from above, you could access the first and last names like this:

    export async function action({ request, params }) {
      const formData = await request.formData();
      const firstName = formData.get("first");
      const lastName = formData.get("last");
      // ...
    }
    

Since we have a handful of form fields, we used [`Object.fromEntries`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/fromEntries)
 to collect them all into an object, which is exactly what our `updateContact` function wants.

    const updates = Object.fromEntries(formData);
    updates.first; // "Some"
    updates.last; // "Name"
    

Aside from `action`, none of these APIs we're discussing are provided by React Router: [`request`](https://developer.mozilla.org/en-US/docs/Web/API/Request)
, [`request.formData`](https://developer.mozilla.org/en-US/docs/Web/API/Request/formData)
, [`Object.fromEntries`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/fromEntries)
 are all provided by the web platform.

After we finished the action, note the [`redirect`](../fetch/redirect)
 at the end:

    export async function action({ request, params }) {
      const formData = await request.formData();
      const updates = Object.fromEntries(formData);
      await updateContact(params.contactId, updates);
      return redirect(`/contacts/${params.contactId}`);
    }
    

Loaders and actions can both [return a `Response`](../route/loader#returning-responses)
 (makes sense, since they received a [`Request`](https://developer.mozilla.org/en-US/docs/Web/API/Request)
!). The [`redirect`](../fetch/redirect)
 helper just makes it easier to return a [response](https://developer.mozilla.org/en-US/docs/Web/API/Response)
 that tells the app to change locations.

Without client side routing, if a server redirected after a POST request, the new page would fetch the latest data and render. As we learned before, React Router emulates this model and automatically revalidates the data on the page after the action. That's why the sidebar automatically updates when we save the form. The extra revalidation code doesn't exist without client side routing, so it doesn't need to exist with client side routing either!

[](#redirecting-new-records-to-the-edit-page)
Redirecting new records to the edit page
--------------------------------------------------------------------------------------

Now that we know how to redirect, let's update the action that creates new contacts to redirect to the edit page:

👉 **Redirect to the new record's edit page**

    import {
      Outlet,
      Link,
      useLoaderData,
      Form,
      redirect,
    } from "react-router-dom";
    import { getContacts, createContact } from "../contacts";
    
    export async function action() {
      const contact = await createContact();
      return redirect(`/contacts/${contact.id}/edit`);
    }
    

Now when we click "New", we should end up on the edit page:

![](/_docs/tutorial/13.webp)

👉 **Add a handful of records**

I'm going to use the stellar lineup of speakers from the first Remix Conference 😁

![](/_docs/tutorial/14.webp)

[](#active-link-styling)
Active Link Styling
--------------------------------------------

Now that we have a bunch of records, it's not clear which one we're looking at in the sidebar. We can use [`NavLink`](../components/nav-link)
 to fix this.

👉 **Use a `NavLink` in the sidebar**

    import {
      Outlet,
      NavLink,
      useLoaderData,
      Form,
      redirect,
    } from "react-router-dom";
    
    export default function Root() {
      return (
        <>
          <div id="sidebar">
            {/* other code */}
    
            <nav>
              {contacts.length ? (
                <ul>
                  {contacts.map((contact) => (
                    <li key={contact.id}>
                      <NavLink
                        to={`contacts/${contact.id}`}
                        className={({ isActive, isPending }) =>
                          isActive
                            ? "active"
                            : isPending
                            ? "pending"
                            : ""
                        }
                      >
                        {/* other code */}
                      </NavLink>
                    </li>
                  ))}
                </ul>
              ) : (
                <p>{/* other code */}</p>
              )}
            </nav>
          </div>
        </>
      );
    }
    

Note that we are passing a function to `className`. When the user is at the URL in the `NavLink`, then `isActive` will be true. When it's _about_ to be active (the data is still loading) then `isPending` will be true. This allows us to easily indicate where the user is, as well as provide immediate feedback on links that have been clicked but we're still waiting for data to load.

![](/_docs/tutorial/15.webp)

[](#global-pending-ui)
Global Pending UI
----------------------------------------

As the user navigates the app, React Router will _leave the old page up_ as data is loading for the next page. You may have noticed the app feels a little unresponsive as you click between the list. Let's provide the user with some feedback so the app doesn't feel unresponsive.

React Router is managing all of the state behind the scenes and reveals the pieces of it you need to build dynamic web apps. In this case, we'll use the [`useNavigation`](../hooks/use-navigation)
 hook.

👉 **`useNavigation` to add global pending UI**

    import {
      // existing code
      useNavigation,
    } from "react-router-dom";
    
    // existing code
    
    export default function Root() {
      const { contacts } = useLoaderData();
      const navigation = useNavigation();
    
      return (
        <>
          <div id="sidebar">{/* existing code */}</div>
          <div
            id="detail"
            className={
              navigation.state === "loading" ? "loading" : ""
            }
          >
            <Outlet />
          </div>
        </>
      );
    }
    

[`useNavigation`](../hooks/use-navigation)
 returns the current navigation state: it can be one of `"idle" | "submitting" | "loading"`.

In our case, we add a `"loading"` class to the main part of the app if we're not idle. The CSS then adds a nice fade after a short delay (to avoid flickering the UI for fast loads). You could do anything you want though, like show a spinner or loading bar across the top.

![](/_docs/tutorial/16.webp)

Note that our data model (`src/contacts.js`) has a clientside cache, so navigating to the same contact is fast the second time. This behavior is _not_ React Router, it will re-load data for changing routes no matter if you've been there before or not. It does, however, avoid calling the loaders for _unchanging_ routes (like the list) during a navigation.

[](#deleting-records)
Deleting Records
--------------------------------------

If we review code in the contact route, we can find the delete button looks like this:

    <Form
      method="post"
      action="destroy"
      onSubmit={(event) => {
        if (
          !confirm(
            "Please confirm you want to delete this record."
          )
        ) {
          event.preventDefault();
        }
      }}
    >
      <button type="submit">Delete</button>
    </Form>
    

Note the `action` points to `"destroy"`. Like `<Link to>`, `<Form action>` can take a _relative_ value. Since the form is rendered in `contact/:contactId`, then a relative action with `destroy` will submit the form to `contact/:contactId/destroy` when clicked.

At this point you should know everything you need to know to make the delete button work. Maybe give it a shot before moving on? You'll need:

1.  A new route
2.  An `action` at that route
3.  `deleteContact` from `src/contacts.js`

👉 **Create the "destroy" route module**

    touch src/routes/destroy.jsx
    

👉 **Add the destroy action**

    import { redirect } from "react-router-dom";
    import { deleteContact } from "../contacts";
    
    export async function action({ params }) {
      await deleteContact(params.contactId);
      return redirect("/");
    }
    

👉 **Add the destroy route to the route config**

    /* existing code */
    import { action as destroyAction } from "./routes/destroy";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        /* existing root route props */\
        children: [\
          /* existing routes */\
          {\
            path: "contacts/:contactId/destroy",\
            action: destroyAction,\
          },\
        ],\
      },\
    ]);
    
    /* existing code */
    

Alright, navigate to a record and click the "Delete" button. It works!

> 😅 I'm still confused why this all works

When the user clicks the submit button:

1.  `<Form>` prevents the default browser behavior of sending a new POST request to the server, but instead emulates the browser by creating a POST request with client side routing
2.  The `<Form action="destroy">` matches the new route at `"contacts/:contactId/destroy"` and sends it the request
3.  After the action redirects, React Router calls all of the loaders for the data on the page to get the latest values (this is "revalidation"). `useLoaderData` returns new values and causes the components to update!

Add a form, add an action, React Router does the rest.

[](#contextual-errors)
Contextual Errors
----------------------------------------

Just for kicks, throw an error in the destroy action:

    export async function action({ params }) {
      throw new Error("oh dang!");
      await deleteContact(params.contactId);
      return redirect("/");
    }
    

![](/_docs/tutorial/17.webp)

Recognize that screen? It's our [`errorElement`](../route/error-element)
 from before. The user, however, can't really do anything to recover from this screen except to hit refresh.

Let's create a contextual error message for the destroy route:

    [\
      /* other routes */\
      {\
        path: "contacts/:contactId/destroy",\
        action: destroyAction,\
        errorElement: <div>Oops! There was an error.</div>,\
      },\
    ];
    

Now try it again:

![](/_docs/tutorial/18.webp)

Our user now has more options than slamming refresh, they can continue to interact with the parts of the page that aren't having trouble 🙌

Because the destroy route has its own `errorElement` and is a child of the root route, the error will render there instead of the root. As you probably noticed, these errors bubble up to the nearest `errorElement`. Add as many or as few as you like, as long as you've got one at the root.

[](#index-routes)
Index Routes
------------------------------

When we load up the app, you'll notice a big blank page on the right side of our list.

![](/_docs/tutorial/19.webp)

When a route has children, and you're at the parent route's path, the `<Outlet>` has nothing to render because no children match. You can think of index routes as the default child route to fill in that space.

👉 **Create the index route module**

    touch src/routes/index.jsx
    

👉 **Fill in the index component's elements**

Feel free to copy paste, nothing special here.

    export default function Index() {
      return (
        <p id="zero-state">
          This is a demo for React Router.
          <br />
          Check out{" "}
          <a href="https://reactrouter.com">
            the docs at reactrouter.com
          </a>
          .
        </p>
      );
    }
    

👉 **Configure the index route**

    // existing code
    import Index from "./routes/index";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          { index: true, element: <Index /> },\
          /* existing routes */\
        ],\
      },\
    ]);
    

Note the [`{ index:true }`](../route/route#index)
 instead of [`{ path: "" }`](../route/route#path)
. That tells the router to match and render this route when the user is at the parent route's exact path, so there are no other child routes to render in the `<Outlet>`.

![](/_docs/tutorial/20.webp)

Voila! No more blank space. It's common to put dashboards, stats, feeds, etc. at index routes. They can participate in data loading as well.

[](#cancel-button)
Cancel Button
--------------------------------

On the edit page we've got a cancel button that doesn't do anything yet. We'd like it to do the same thing as the browser's back button.

We'll need a click handler on the button as well as [`useNavigate`](../hooks/use-navigate)
 from React Router.

👉 **Add the cancel button click handler with `useNavigate`**

    import {
      Form,
      useLoaderData,
      redirect,
      useNavigate,
    } from "react-router-dom";
    
    export default function EditContact() {
      const { contact } = useLoaderData();
      const navigate = useNavigate();
    
      return (
        <Form method="post" id="contact-form">
          {/* existing code */}
    
          <p>
            <button type="submit">Save</button>
            <button
              type="button"
              onClick={() => {
                navigate(-1);
              }}
            >
              Cancel
            </button>
          </p>
        </Form>
      );
    }
    

Now when the user clicks "Cancel", they'll be sent back one entry in the browser's history.

> 🧐 Why is there no `event.preventDefault` on the button?

A `<button type="button">`, while seemingly redundant, is the HTML way of preventing a button from submitting its form.

Two more features to go. We're on the home stretch!

[](#url-search-params-and-get-submissions)
URL Search Params and GET Submissions
--------------------------------------------------------------------------------

All of our interactive UI so far have been either links that change the URL or forms that post data to actions. The search field is interesting because it's a mix of both: it's a form but it only changes the URL, it doesn't change data.

Right now it's just a normal HTML `<form>`, not a React Router `<Form>`. Let's see what the browser does with it by default:

👉 **Type a name into the search field and hit the enter key**

Note the browser's URL now contains your query in the URL as [URLSearchParams](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams)
:

    http://127.0.0.1:5173/?q=ryan
    

If we review the search form, it looks like this:

    <form id="search-form" role="search">
      <input
        id="q"
        aria-label="Search contacts"
        placeholder="Search"
        type="search"
        name="q"
      />
      <div id="search-spinner" aria-hidden hidden={true} />
      <div className="sr-only" aria-live="polite"></div>
    </form>
    

As we've seen before, browsers can serialize forms by the `name` attribute of it's input elements. The name of this input is `q`, that's why the URL has `?q=`. If we named it `search` the URL would be `?search=`.

Note that this form is different from the others we've used, it does not have `<form method="post">`. The default `method` is `"get"`. That means when the browser creates the request for the next document, it doesn't put the form data into the request POST body, but into the [`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams)
 of a GET request.

[](#get-submissions-with-client-side-routing)
GET Submissions with Client Side Routing
--------------------------------------------------------------------------------------

Let's use client side routing to submit this form and filter the list in our existing loader.

👉 **Change `<form>` to `<Form>`**

    <Form id="search-form" role="search">
      <input
        id="q"
        aria-label="Search contacts"
        placeholder="Search"
        type="search"
        name="q"
      />
      <div id="search-spinner" aria-hidden hidden={true} />
      <div className="sr-only" aria-live="polite"></div>
    </Form>
    

👉 **Filter the list if there are URLSearchParams**

    export async function loader({ request }) {
      const url = new URL(request.url);
      const q = url.searchParams.get("q");
      const contacts = await getContacts(q);
      return { contacts };
    }
    

![](/_docs/tutorial/21.webp)

Because this is a GET, not a POST, React Router _does not_ call the `action`. Submitting a GET form is the same as clicking a link: only the URL changes. That's why the code we added for filtering is in the `loader`, not the `action` of this route.

This also means it's a normal page navigation. You can click the back button to get back to where you were.

[](#synchronizing-urls-to-form-state)
Synchronizing URLs to Form State
----------------------------------------------------------------------

There are a couple of UX issues here that we can take care of quickly.

1.  If you click back after a search, the form field still has the value you entered even though the list is no longer filtered.
2.  If you refresh the page after searching, the form field no longer has the value in it, even though the list is filtered

In other words, the URL and our form state are out of sync.

👉 **Return `q` from your loader and set it as the search field default value**

    // existing code
    
    export async function loader({ request }) {
      const url = new URL(request.url);
      const q = url.searchParams.get("q");
      const contacts = await getContacts(q);
      return { contacts, q };
    }
    
    export default function Root() {
      const { contacts, q } = useLoaderData();
      const navigation = useNavigation();
    
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <Form id="search-form" role="search">
                <input
                  id="q"
                  aria-label="Search contacts"
                  placeholder="Search"
                  type="search"
                  name="q"
                  defaultValue={q}
                />
                {/* existing code */}
              </Form>
              {/* existing code */}
            </div>
            {/* existing code */}
          </div>
          {/* existing code */}
        </>
      );
    }
    

That solves problem (2). If you refresh the page now, the input field will show the query.

![](/_docs/tutorial/21.webp)

Now for problem (1), clicking the back button and updating the input. We can bring in `useEffect` from React to manipulate the form's state in the DOM directly.

👉 **Synchronize input value with the URL Search Params**

    import { useEffect } from "react";
    
    // existing code
    
    export default function Root() {
      const { contacts, q } = useLoaderData();
      const navigation = useNavigation();
    
      useEffect(() => {
        document.getElementById("q").value = q;
      }, [q]);
    
      // existing code
    }
    

> 🤔 Shouldn't you use a controlled component and React State for this?

You could certainly do this as a controlled component, but you'll end up with more complexity for the same behavior. You don't control the URL, the user does with the back/forward buttons. There would be more synchronization points with a controlled component.

If you're still concerned, expand this to see what it would look like

Notice how controlling the input requires three points of synchronization now instead of just one. The behavior is identical but the code is more complex.

    import { useEffect, useState } from "react";
    // existing code
    
    export async function loader({ request }) {
      const url = new URL(request.url);
      const q = url.searchParams.get("q") || "";
      const contacts = await getContacts(q);
      return { contacts, q };
    }
    
    // existing code
    
    export default function Root() {
      const { contacts, q } = useLoaderData();
      const [query, setQuery] = useState(q);
      const navigation = useNavigation();
    
      useEffect(() => {
        setQuery(q);
      }, [q]);
    
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <Form id="search-form" role="search">
                <input
                  id="q"
                  aria-label="Search contacts"
                  placeholder="Search"
                  type="search"
                  name="q"
                  value={query}
                  onChange={(e) => {
                    setQuery(e.target.value);
                  }}
                />
                {/* existing code */}
              </Form>
              {/* existing code */}
            </div>
            {/* existing code */}
          </div>
        </>
      );
    }

[](#submitting-forms-onchange)
Submitting Forms `onChange`
----------------------------------------------------------

We've got a product decision to make here. For this UI, we'd probably rather have the filtering happen on every key stroke instead of when the form is explicitly submitted.

We've seen `useNavigate` already, we'll use its cousin, [`useSubmit`](../hooks/use-submit)
, for this.

    // existing code
    import {
      // existing code
      useSubmit,
    } from "react-router-dom";
    
    export default function Root() {
      const { contacts, q } = useLoaderData();
      const navigation = useNavigation();
      const submit = useSubmit();
    
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <Form id="search-form" role="search">
                <input
                  id="q"
                  aria-label="Search contacts"
                  placeholder="Search"
                  type="search"
                  name="q"
                  defaultValue={q}
                  onChange={(event) => {
                    submit(event.currentTarget.form);
                  }}
                />
                {/* existing code */}
              </Form>
              {/* existing code */}
            </div>
            {/* existing code */}
          </div>
          {/* existing code */}
        </>
      );
    }
    

Now as you type, the form is submitted automatically!

Note the argument to [`submit`](../hooks/use-submit)
. We're passing in `event.currentTarget.form`. The `currentTarget` is the DOM node the event is attached to, and the `currentTarget.form` is the input's parent form node. The `submit` function will serialize and submit any form you pass to it.

[](#adding-search-spinner)
Adding Search Spinner
------------------------------------------------

In a production app, it's likely this search will be looking for records in a database that is too large to send all at once and filter client side. That's why this demo has some faked network latency.

Without any loading indicator, the search feels kinda sluggish. Even if we could make our database faster, we'll always have the user's network latency in the way and out of our control. For a better UX, let's add some immediate UI feedback for the search. For this we'll use [`useNavigation`](../hooks/use-navigation)
 again.

👉 **Add the search spinner**

    // existing code
    
    export default function Root() {
      const { contacts, q } = useLoaderData();
      const navigation = useNavigation();
      const submit = useSubmit();
    
      const searching =
        navigation.location &&
        new URLSearchParams(navigation.location.search).has(
          "q"
        );
    
      useEffect(() => {
        document.getElementById("q").value = q;
      }, [q]);
    
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <Form id="search-form" role="search">
                <input
                  id="q"
                  className={searching ? "loading" : ""}
                  // existing code
                />
                <div
                  id="search-spinner"
                  aria-hidden
                  hidden={!searching}
                />
                {/* existing code */}
              </Form>
              {/* existing code */}
            </div>
            {/* existing code */}
          </div>
          {/* existing code */}
        </>
      );
    }
    

![](/_docs/tutorial/22.webp)

The `navigation.location` will show up when the app is navigating to a new URL and loading the data for it. It then goes away when there is no pending navigation anymore.

[](#managing-the-history-stack)
Managing the History Stack
----------------------------------------------------------

Now that the form is submitted for every key stroke, if we type the characters "seba" and then delete them with backspace, we end up with 7 new entries in the stack 😂. We definitely don't want this

![](/_docs/tutorial/23.webp)

We can avoid this by _replacing_ the current entry in the history stack with the next page, instead of pushing into it.

👉 **Use `replace` in `submit`**

    // existing code
    
    export default function Root() {
      // existing code
    
      return (
        <>
          <div id="sidebar">
            <h1>React Router Contacts</h1>
            <div>
              <Form id="search-form" role="search">
                <input
                  id="q"
                  // existing code
                  onChange={(event) => {
                    const isFirstSearch = q == null;
                    submit(event.currentTarget.form, {
                      replace: !isFirstSearch,
                    });
                  }}
                />
                {/* existing code */}
              </Form>
              {/* existing code */}
            </div>
            {/* existing code */}
          </div>
          {/* existing code */}
        </>
      );
    }
    

We only want to replace search results, not the page before we started searching, so we do a quick check if this is the first search or not and then decide to replace.

Each key stroke no longer creates new entries, so the user can click back out of the search results without having to click it 7 times 😅.

[](#mutations-without-navigation)
Mutations Without Navigation
--------------------------------------------------------------

So far all of our mutations (the times we change data) have used forms that navigate, creating new entries in the history stack. While these user flows are common, it's equally as common to want to change data _without_ causing a navigation.

For these cases, we have the [`useFetcher`](../hooks/use-fetcher)
 hook. It allows us to communicate with loaders and actions without causing a navigation.

The ★ button on the contact page makes sense for this. We aren't creating or deleting a new record, we don't want to change pages, we simply want to change the data on the page we're looking at.

👉 **Change the `<Favorite>` form to a fetcher form**

    import {
      useLoaderData,
      Form,
      useFetcher,
    } from "react-router-dom";
    
    // existing code
    
    function Favorite({ contact }) {
      const fetcher = useFetcher();
      const favorite = contact.favorite;
    
      return (
        <fetcher.Form method="post">
          <button
            name="favorite"
            value={favorite ? "false" : "true"}
            aria-label={
              favorite
                ? "Remove from favorites"
                : "Add to favorites"
            }
          >
            {favorite ? "★" : "☆"}
          </button>
        </fetcher.Form>
      );
    }
    

Might want to take a look at that form while we're here. As always, our form has fields with a `name` prop. This form will send [`formData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData)
 with a `favorite` key that's either `"true" | "false"`. Since it's got `method="post"` it will call the action. Since there is no `<fetcher.Form action="...">` prop, it will post to the route where the form is rendered.

👉 **Create the action**

    // existing code
    import { getContact, updateContact } from "../contacts";
    
    export async function action({ request, params }) {
      const formData = await request.formData();
      return updateContact(params.contactId, {
        favorite: formData.get("favorite") === "true",
      });
    }
    
    export default function Contact() {
      // existing code
    }
    

Pretty simple. Pull the form data off the request and send it to the data model.

👉 **Configure the route's new action**

    // existing code
    import Contact, {
      loader as contactLoader,
      action as contactAction,
    } from "./routes/contact";
    
    const router = createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        errorElement: <ErrorPage />,\
        loader: rootLoader,\
        action: rootAction,\
        children: [\
          { index: true, element: <Index /> },\
          {\
            path: "contacts/:contactId",\
            element: <Contact />,\
            loader: contactLoader,\
            action: contactAction,\
          },\
          /* existing code */\
        ],\
      },\
    ]);
    

Alright, we're ready to click the star next to the user's name!

![](/_docs/tutorial/24.webp)

Check that out, both stars automatically update. Our new `<fetcher.Form method="post">` works almost exactly like the `<Form>` we've been using: it calls the action and then all data is revalidated automatically--even your errors will be caught the same way.

There is one key difference though, it's not a navigation--the URL doesn't change, the history stack is unaffected.

[](#optimistic-ui)
Optimistic UI
--------------------------------

You probably noticed the app felt kind of unresponsive when we clicked the favorite button from the last section. Once again, we added some network latency because you're going to have it in the real world!

To give the user some feedback, we could put the star into a loading state with [`fetcher.state`](../hooks/use-fetcher#fetcherstate)
 (a lot like `navigation.state` from before), but we can do something even better this time. We can use a strategy called "optimistic UI"

The fetcher knows the form data being submitted to the action, so it's available to you on `fetcher.formData`. We'll use that to immediately update the star's state, even though the network hasn't finished. If the update eventually fails, the UI will revert to the real data.

👉 **Read the optimistic value from `fetcher.formData`**

    // existing code
    
    function Favorite({ contact }) {
      const fetcher = useFetcher();
    
      const favorite = fetcher.formData
        ? fetcher.formData.get("favorite") === "true"
        : contact.favorite;
    
      return (
        <fetcher.Form method="post">
          <button
            name="favorite"
            value={favorite ? "false" : "true"}
            aria-label={
              favorite
                ? "Remove from favorites"
                : "Add to favorites"
            }
          >
            {favorite ? "★" : "☆"}
          </button>
        </fetcher.Form>
      );
    }
    

If you click the button now you should see the star _immediately_ change to the new state. Instead of always rendering the actual data, we check if the fetcher has any `formData` being submitted, if so, we'll use that instead. When the action is done, the `fetcher.formData` will no longer exist and we're back to using the actual data. So even if you write bugs in your optimistic UI code, it'll eventually go back to the correct state 🥹

[](#not-found-data)
Not Found Data
----------------------------------

What happens if the contact we're trying to load doesn't exist?

![](/_docs/tutorial/25.webp)

Our root [`errorElement`](../route/error-element)
 is catching this unexpected error as we try to render a `null` contact. Nice the error was properly handled, but we can do better!

Whenever you have an expected error case in a loader or action–like the data not existing–you can `throw`. The call stack will break, React Router will catch it, and the error path is rendered instead. We won't even try to render a `null` contact.

👉 **Throw a 404 response in the loader**

    export async function loader({ params }) {
      const contact = await getContact(params.contactId);
      if (!contact) {
        throw new Response("", {
          status: 404,
          statusText: "Not Found",
        });
      }
      return { contact };
    }
    

![](/_docs/tutorial/27.webp)

Instead of hitting a render error with `Cannot read properties of null`, we avoid the component completely and render the error path instead, telling the user something more specific.

This keeps your happy paths, happy. Your route elements don't need to concern themselves with error and loading states.

[](#pathless-routes)
Pathless Routes
------------------------------------

One last thing. The last error page we saw would be better if it rendered inside the root outlet, instead of the whole page. In fact, every error in all of our child routes would be better in the outlet, then the user has more options than hitting refresh.

We'd like it to look like this:

![](/_docs/tutorial/26.webp)

We could add the error element to every one of the child routes but, since it's all the same error page, this isn't recommended.

There's a cleaner way. Routes can be used _without_ a path, which lets them participate in the UI layout without requiring new path segments in the URL. Check it out:

👉 **Wrap the child routes in a pathless route**

    createBrowserRouter([\
      {\
        path: "/",\
        element: <Root />,\
        loader: rootLoader,\
        action: rootAction,\
        errorElement: <ErrorPage />,\
        children: [\
          {\
            errorElement: <ErrorPage />,\
            children: [\
              { index: true, element: <Index /> },\
              {\
                path: "contacts/:contactId",\
                element: <Contact />,\
                loader: contactLoader,\
                action: contactAction,\
              },\
              /* the rest of the routes */\
            ],\
          },\
        ],\
      },\
    ]);
    

When any errors are thrown in the child routes, our new pathless route will catch it and render, preserving the root route's UI!

[](#jsx-routes)
JSX Routes
--------------------------

And for our final trick, many folks prefer to configure their routes with JSX. You can do that with `createRoutesFromElements`. There is no functional difference between JSX or objects when configuring your routes, it's simply a stylistic preference.

    import {
      createRoutesFromElements,
      createBrowserRouter,
      Route,
    } from "react-router-dom";
    
    const router = createBrowserRouter(
      createRoutesFromElements(
        <Route
          path="/"
          element={<Root />}
          loader={rootLoader}
          action={rootAction}
          errorElement={<ErrorPage />}
        >
          <Route errorElement={<ErrorPage />}>
            <Route index element={<Index />} />
            <Route
              path="contacts/:contactId"
              element={<Contact />}
              loader={contactLoader}
              action={contactAction}
            />
            <Route
              path="contacts/:contactId/edit"
              element={<EditContact />}
              loader={contactLoader}
              action={editAction}
            />
            <Route
              path="contacts/:contactId/destroy"
              action={destroyAction}
            />
          </Route>
        </Route>
      )
    );
    

* * *

That's it! Thanks for giving React Router a shot. We hope this tutorial gives you a solid start to build great user experiences. There's a lot more you can do with React Router, so make sure to check out all the APIs 😀

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Examples v6.30.0 | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

6.30.0

Branches

[latest (7.6.0)](/home)
[dev](/dev/)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Examples

[](#examples)
Examples
======================

You can find many examples, including running version of them on StackBlitz in the GitHub repository:

[https://github.com/remix-run/react-router/tree/dev/examples](https://github.com/remix-run/react-router/tree/dev/examples)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

---

# Navigating  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/data/navigating)
[dev](/dev/start/data/navigating)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Navigating

[](#navigating)
Navigating
==========================

Navigating in Data Mode is the same as Framework Mode, please see the [Navigating](../framework/navigating)
 guide for more information.

* * *

Next: [Pending UI](./pending-ui)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/data/navigating.md)

---

# Actions  | React Router

![](/assets/icons-C24Z-wDY.svg)

[](/home)

latest

Branches

[latest (7.6.0)](/start/data/actions)
[dev](/dev/start/data/actions)

Versions

[7.6.0](/7.6.0/home)
[6.30.0](/6.30.0)
[v4/5.x](https://v5.reactrouter.com/)
[v3.x](https://github.com/remix-run/react-router/tree/v3.2.6/docs)

[API Reference](https://api.reactrouter.com/v7/)

Search Light Dark System

[](https://github.com/remix-run/react-router "View code on GitHub")
[](https://rmx.as/discord "Chat on Discord")

Actions

On this page

*   [Defining Actions](/start/data/actions#defining-actions)
    
*   [Calling Actions](/start/data/actions#calling-actions)
    
*   [Calling actions with a Form](/start/data/actions#calling-actions-with-a-form)
    
*   [Calling actions with useSubmit](/start/data/actions#calling-actions-with-usesubmit)
    
*   [Calling actions with a fetcher](/start/data/actions#calling-actions-with-a-fetcher)
    
*   [Accessing Action Data](/start/data/actions#accessing-action-data)
    

*   [Defining Actions](/start/data/actions#defining-actions)
    
*   [Calling Actions](/start/data/actions#calling-actions)
    
*   [Calling actions with a Form](/start/data/actions#calling-actions-with-a-form)
    
*   [Calling actions with useSubmit](/start/data/actions#calling-actions-with-usesubmit)
    
*   [Calling actions with a fetcher](/start/data/actions#calling-actions-with-a-fetcher)
    
*   [Accessing Action Data](/start/data/actions#accessing-action-data)
    

[](#actions)
Actions
====================

*   [Framework](../../start/modes "Not available with Framework")
    
*   [Data](../../start/modes "Available with Data")
    
*   [Declarative](../../start/modes "Not available with Declarative")
    

[](#defining-actions)
Defining Actions
--------------------------------------

Data mutations are done through Route actions defined on the `action` property of a route object. When the action completes, all loader data on the page is revalidated to keep your UI in sync with the data without writing any code to do it.

    import { createBrowserRouter } from "react-router";
    import { someApi } from "./api";
    
    let router = createBrowserRouter([\
      {\
        path: "/projects/:projectId",\
        Component: Project,\
        action: async ({ request }) => {\
          let formData = await request.formData();\
          let title = formData.get("title");\
          let project = await someApi.updateProject({ title });\
          return project;\
        },\
      },\
    ]);
    

[](#calling-actions)
Calling Actions
------------------------------------

Actions are called declaratively through `<Form>` and imperatively through `useSubmit` (or `<fetcher.Form>` and `fetcher.submit`) by referencing the route's path and a "post" method.

### [](#calling-actions-with-a-form)
Calling actions with a Form

    import { Form } from "react-router";
    
    function SomeComponent() {
      return (
        <Form action="/projects/123" method="post">
          <input type="text" name="title" />
          <button type="submit">Submit</button>
        </Form>
      );
    }
    

This will cause a navigation and a new entry will be added to the browser history.

### [](#calling-actions-with-usesubmit)
Calling actions with useSubmit

You can submit form data to an action imperatively with `useSubmit`.

    import { useCallback } from "react";
    import { useSubmit } from "react-router";
    import { useFakeTimer } from "fake-lib";
    
    function useQuizTimer() {
      let submit = useSubmit();
    
      let cb = useCallback(() => {
        submit(
          { quizTimedOut: true },
          { action: "/end-quiz", method: "post" }
        );
      }, []);
    
      let tenMinutes = 10 * 60 * 1000;
      useFakeTimer(tenMinutes, cb);
    }
    

This will cause a navigation and a new entry will be added to the browser history.

### [](#calling-actions-with-a-fetcher)
Calling actions with a fetcher

Fetchers allow you to submit data to actions (and loaders) without causing a navigation (no new entries in the browser history).

    import { useFetcher } from "react-router";
    
    function Task() {
      let fetcher = useFetcher();
      let busy = fetcher.state !== "idle";
    
      return (
        <fetcher.Form method="post" action="/update-task/123">
          <input type="text" name="title" />
          <button type="submit">
            {busy ? "Saving..." : "Save"}
          </button>
        </fetcher.Form>
      );
    }
    

They also have the imperative `submit` method.

    fetcher.submit(
      { title: "New Title" },
      { action: "/update-task/123", method: "post" }
    );
    

See the [Using Fetchers](../../how-to/fetchers)
 guide for more information.

[](#accessing-action-data)
Accessing Action Data
------------------------------------------------

Actions can return data available through `useActionData` in the route component or `fetcher.data` when using a fetcher.

    function Project() {
      let actionData = useActionData();
      return (
        <div>
          <h1>Project</h1>
          <Form method="post">
            <input type="text" name="title" />
            <button type="submit">Submit</button>
          </Form>
          {actionData ? (
            <p>{actionData.title} updated</p>
          ) : null}
        </div>
      );
    }
    

* * *

Next: [Navigating](./navigating)

[Brand Assets](/brand)

•

Docs and examples [CC 4.0](https://creativecommons.org/licenses/by/4.0/)

[Edit](https://github.com/remix-run/react-router/edit/main/docs/start/data/actions.md)

---