React Router shows a blank page and warns about a leaf route
Matched leaf route at location "/" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.Short answer
React Router prints this warning in development when the deepest matched route has no element, Component or lazy. It then renders an empty Outlet, so the page is blank. Give that route an element or Component, or make the path you visit match a route that has one.
Fix it fast
1Find out which cause you have
Read the location in the warning, then look in your route config for the route that matches it. Check whether that exact route object has element, Component or lazy.
grep -rn "createBrowserRouter\|<Routes\|<Route " src/2Match what you see, then jump to its fix
- 1
The warning names the URL you opened, and the route for it is written with path and no elementThe route that matches has only a path or childrenFix - 2
The route looks complete in JSX, but the warning still firesAn element or Component is written with the wrong property name or formFix - 3
The parent layout appears, but the area for the child stays emptyThe parent route renders no Outlet, or the index route is missingFix
- 1
What does the error look like?
Matched leaf route at location "/" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.
Cause 1 of 3
The route that matches has only a path or children
1Check
A route with a path and no component only adds a path prefix for its children; it renders no UI of its own. If the URL equals that prefix and no child matches, nothing is left to render.
grep -rn "path: \"/\"\|path=\"/\"" src/2Fix
Add the component to the route, or give the group an index child that renders at the parent's own URL.
createBrowserRouter([
{
path: "/",
Component: Root,
children: [
{ index: true, Component: Home },
{ path: "about", Component: About },
],
},
]);3Verify
Open the URL from the warning again: the page renders and the console is quiet.
npm run devConfirmed by reactrouter.com
Cause 2 of 3
An element or Component is written with the wrong property name or form
1Check
In the declarative API a route takes element with a created element, or Component with a component reference. Data-router objects use Component. A misspelled property or a component passed where an element is expected leaves the route empty.
grep -rn "element=\|Component=" src/2Fix
Use one of the documented forms on every route that should render something.
<Route path="/for-sale" element={<Properties />} />
<Route path="/for-sale" Component={Properties} />3Verify
The route renders its component at the URL.
npm run devConfirmed by reactrouter.com
Cause 3 of 3
The parent route renders no Outlet, or the index route is missing
1Check
Children render into the parent's Outlet. An index route is the default child shown at the parent's URL. Without an Outlet in the parent, or without an index child, the child area is empty.
grep -rn "Outlet" src/2Fix
Render an Outlet in the parent component and add an index route for the parent's own URL.
import { Outlet } from "react-router";
export default function Dashboard() {
return (
<div>
<h1>Dashboard</h1>
<Outlet />
</div>
);
}3Verify
Visit the parent URL and a child URL: both fill the Outlet.
npm run devConfirmed by reactrouter.com
How do I stop it coming back?
- Give every route either a component, or children that end in routes with components.
- Keep an index route in every group of nested routes.
- Open the dev console after adding a route: the warning is only printed in development builds.
- Keep the router in one file so a route list can be read from top to bottom.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix