Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →React Router Data Mode is the router approach in which you define routes outside the React component tree and connect them to route-specific data loading, mutations, and pending states. It is a fit when you want those data-routing features but still want to control how your app handles bundling, data, and server abstractions. The official guide describes React Router as “a multi-strategy router for React.” React Router’s mode guide compares Declarative, Data, and Framework modes.
What is React Router Data Mode?
Data Mode uses data-router APIs such as createBrowserRouter and RouterProvider. Instead of expressing the route configuration inside rendered React components, you define it separately, then provide the resulting router to React. Routes can declare a loader for data and an action for mutations.
A minimal browser-router setup looks like this:
import { createBrowserRouter, RouterProvider } from "react-router";
const router = createBrowserRouter([
{
path: "/",
Component: Root,
loader: loadRootData,
},
]);
ReactDOM.createRoot(root).render(<RouterProvider router={router} />);This is an illustration of the documented API, not a complete application: Root and loadRootData must be defined, and the component reads its route data through the appropriate React Router APIs. In this structure, the loader is associated with the route rather than being an ad hoc fetch initiated by the component after it renders.
How do loaders, actions, and forms fit together?
Load route data with a loader
A route’s loader supplies data for that route. This puts data requirements alongside the route definition, so navigation and route rendering can work with the route’s data as part of the same routing model.
#1 Best Overall
Mutate data with an action
A route’s action handles a mutation. An action receives a request; it can read submitted values from FormData and pass them to application logic. React Router documents calling actions through <Form> or useSubmit. The Data Mode actions guide covers these submission patterns.
Choose navigation or a fetcher submission
Use <Form> when submission belongs in the navigation flow: it integrates with pending navigation state. Use a fetcher form or fetcher.submit when the interaction should submit without causing navigation. That distinction is useful for choosing the right UI behavior, not just the API syntax: a navigation changes the active route, while a fetcher supports a local interaction that can stay on the current route.
What happens after an action?
After an action completes, React Router revalidates loader data by default, allowing the UI to reflect the result without manually coordinating refreshes in every component. Revalidation also occurs for some navigations, as loaders may need to provide data that matches the current route state.
That default is convenient, but it can do unnecessary work if loaders are expensive and a particular mutation cannot affect their data. In such cases, React Router provides route-level shouldRevalidate and a call-site defaultShouldRevalidate option to make a targeted decision. Use these controls only where you can establish that skipping revalidation is correct; disabling it broadly can leave route data out of sync. See the revalidation optimization guide.
How does Data Mode compare with Declarative and Framework modes?
The three modes add capabilities while shifting how much of the application’s routing architecture React Router supplies. The official guide presents the choice as a trade-off between built-in features and architectural control.
| Mode | What it provides | When it fits |
|---|---|---|
| Declarative | Basic URL matching and navigation, without Data Mode’s route loaders and actions. | Choose it when routing needs are simple or another data layer already provides the pending-state and data abstractions you want. |
| Data | Route configuration outside React rendering, plus loaders, actions, pending states, and related data-router APIs. | Choose it when you want route-aware data features while keeping control over bundling, data, and server abstractions. It is also a natural fit for a team already using a v6.4 data router and satisfied with that architecture. |
| Framework | Data Mode with additional framework tooling and route-module features, including the Vite plugin, type-safe route APIs, code splitting, and SPA, SSR, or static-rendering strategies described in the mode guide. | Consider it when you want more of those capabilities integrated instead of assembling the architecture yourself. |
Framework Mode is not behavior that Data Mode automatically supplies: the guide describes Framework Mode as wrapping Data Mode with additional tooling and route-module features. The right choice depends on how much you want the router to handle versus how much architectural control you want to retain. The official mode guide sets out that distinction.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which mode should you start with?
- Start with Declarative if you only need basic matching and navigation, or if another layer already handles data loading and pending UI.
- Choose Data Mode if loaders, actions, and navigation-aware pending states are useful, but you want to own more of the surrounding architecture.
- Consider Framework Mode if you want the documented Vite integration, route-module capabilities, and rendering strategies as part of a broader framework setup.
React Router also publishes react-router-dom in v7 as a re-export of react-router, according to its changelog. Because that changelog is actively updated with API and flag changes, check the release entry for your installed version when following version-sensitive guidance.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
