useNavigate and Link throw because no router is above them
Uncaught Error: useNavigate() may be used only in the context of a <Router> component.Short answer
Router hooks and Link read the router from React context. If the component renders outside BrowserRouter or MemoryRouter, there is no router to read and the call throws. In the app, mount the router above everything that navigates. In tests, wrap the component in MemoryRouter.
Fix it fast
1Find out which cause you have
Find the component named in the stack trace and walk up to see whether a router wraps it, in the app entry and in the test render call.
grep -rn "BrowserRouter\|MemoryRouter\|RouterProvider\|createRoot" src2Match what you see, then jump to its fix
- 1
The error appears only under jest or vitest, while the running app worksThe component that navigates renders in a test without a routerFix - 2
The app itself crashes on first render; Link or useNavigate sits in the same file that creates the routerThe router is mounted below the component, or not at allFix
- 1
What does the error look like?
Uncaught Error: useNavigate() may be used only in the context of a <Router> component.Cannot destructure property 'basename' of 'React2.useContext(...)' as it is null
Cause 1 of 2
The component that navigates renders in a test without a router
1Check
A test renders the component alone. Nothing in that tree is a router, so the context is empty.
grep -rn "render(" src --include=*.test.*2Fix
Give render a router. MemoryRouter lets you choose the starting URL, and render's wrapper option avoids repeating it.
import { render } from '@testing-library/react';
import { MemoryRouter } from 'react-router';
render(<Header />, { wrapper: MemoryRouter });
// or choose the start URL
render(
<MemoryRouter initialEntries={['/account']}>
<Header />
</MemoryRouter>
);3Verify
Run the test file.
npx vitest run src/Header.test.tsxConfirmed by testing-library.com
Cause 2 of 2
The router is mounted below the component, or not at all
1Check
The docs require the router to wrap every component that uses Link, Routes or router hooks. A router created inside App cannot serve App's own hooks.
sed -n 1,30p src/main.tsx2Fix
Render the router where React is mounted, and import from react-router.
import { createRoot } from 'react-dom/client';
import { BrowserRouter } from 'react-router';
import App from './App';
createRoot(document.getElementById('root')!).render(
<BrowserRouter>
<App />
</BrowserRouter>
);3Verify
Reload the page and click a link.
npm run devConfirmed by reactrouter.com
How do I stop it coming back?
- Write one renderWithRouter test helper and use it for every component that has a link.
- Keep the router in the app entry file, not in App.
- Call navigate from event handlers or effects, never during render.
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
useRoutes() fails because no Router wraps the component
Error: useRoutes() may be used only in the context of a <Router> component.
useRoutes reads the location that a router provides to the components below it.
2 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