React Router Data Loaders: Fetch Before You Render

Why it exists

To solve the common "fetch-on-render" waterfall. Traditionally, a component mounts, then triggers a useEffect hook to fetch data, showing a loading spinner while it waits. This creates a sequential load: render the component shell, then fetch data, then re-render with data. Loaders were created to run the data fetch in parallel with the code download for the next page, eliminating the waterfall.

The mental model

Think of a loader as a "pre-flight check" for a route. Before React Router even tries to render the components for a URL like /products/123, it first finds and executes the loader function associated with that route. The component doesn't render until the loader's promise resolves and the data is ready. This guarantees data is available on the first render.

How it works

You define an async function called loader on your route configuration. This function receives context, including params from the URL and the request object. Inside the loader, you perform your data fetch and return the data. React Router calls this function during navigation and makes the data available to your component via the useLoaderData hook. Error handling is also built-in; if a loader throws an error, it's caught and can be displayed using an errorElement.

When to use it

Use loaders for the critical data a route needs to render its primary content. This is ideal for product detail pages, user profiles, or dashboard screens. It dramatically simplifies component logic by removing the need for useEffect, useState for loading and error states, and manual data fetching orchestration. The component becomes a simple, declarative view of the data it receives.

When not to use it

Avoid loaders for data that is not essential for the initial render, like secondary content loaded after the main view is interactive. Also, for data triggered by user interactions within a component (like a search-as-you-type input), use a fetcher (useFetcher) instead, as it doesn't trigger a full navigation.

One canonical example

A route for a product page, /products/:id, would have a loader function. This async function loader({ params }) would take the params object, extract params.id, and fetch data from an API endpoint like /api/products/${params.id}. The component for this route would then call const product = useLoaderData(); to get the product details synchronously, without any internal loading state.