Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

useNavigate and Link throw because no router is above them

ErrorUncaught 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.

  • Applies to react-router 7, React 19, Testing Library
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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" src
  2. 2Match what you see, then jump to its fix

    1. 1The error appears only under jest or vitest, while the running app worksThe component that navigates renders in a test without a routerFix
    2. 2The 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

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.tsx

Confirmed by testing-library.com

Did this fix it?

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.tsx

2Fix

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 dev

Confirmed by reactrouter.com

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.