useRoutes() fails because no Router wraps the component
Error: useRoutes() may be used only in the context of a <Router> component.Short answer
useRoutes reads the location that a router provides to the components below it. The error means the component calling it sits above the router or outside any router. Move BrowserRouter up to where React is mounted, so App renders inside it, and give tests a MemoryRouter.
Fix it fast
1Find out which cause you have
Find the component that calls useRoutes and the place where the router is created. The router must be an ancestor of the caller, not a sibling or a child.
grep -rn "useRoutes\|BrowserRouter\|createBrowserRouter" src2Match what you see, then jump to its fix
- 1
One file contains both <BrowserRouter> and a useRoutes() call, and the hook sits above the JSX that renders the routerApp calls useRoutes and renders the Router in the same componentFix - 2
The app works in the browser but the same error appears in a unit testA test renders the component without any routerFix
- 1
What does the error look like?
Error: useRoutes() may be used only in the context of a <Router> component.
Cause 1 of 2
App calls useRoutes and renders the Router in the same component
1Check
A router provides location context to everything rendered inside it. Hooks that run in the same component body run before that component has rendered anything, so no router exists above them yet.
grep -n -E 'BrowserRouter|useRoutes' src/App.jsx src/main.jsx src/index.js2Fix
Wrap App in the router where you call createRoot, and keep useRoutes inside App.
// main.jsx
import { createRoot } from "react-dom/client";
import { BrowserRouter } from "react-router";
import App from "./App";
createRoot(document.getElementById("root")).render(
<BrowserRouter>
<App />
</BrowserRouter>
);
// App.jsx
import { useRoutes } from "react-router";
export default function App() {
return useRoutes(routes);
}3Verify
Start the dev server and open a route; the app renders and the error is gone.
npm run devConfirmed by reactrouter.com
Cause 2 of 2
A test renders the component without any router
1Check
In a test there is no main entry file, so nothing wraps the component. The React Router docs name MemoryRouter and createMemoryRouter as the routers that suit tests, because they do not need the browser history API.
grep -rn "render(" src --include=*.test.*2Fix
Wrap the component under test in a MemoryRouter, with the starting URL you want.
import { render } from "@testing-library/react";
import { MemoryRouter } from "react-router";
render(
<MemoryRouter initialEntries={["/dashboard"]}>
<App />
</MemoryRouter>
);3Verify
Run the test file.
npx vitest run src/App.test.jsxConfirmed by reactrouter.com
How do I stop it coming back?
- Pick one router style per app, as the React Router docs advise, and mount it once where React is mounted.
- Create a small test helper that wraps components in MemoryRouter, so each test does not repeat it.
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
Switch, Redirect or useHistory missing after a React Router upgrade
Attempted import error: 'useHistory' is not exported from 'react-router-dom'
React Router v6 removed Switch.
3 causes, each with a fixWeb 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 fix