Error: NextRouter was not mounted
The Problem
When using the useRouter hook in Next.js 13 or later, you may encounter the following error:
Error: NextRouter was not mounted
This error can occur in one of two ways:
- When a component uses the
useRouterhook outside of a Next.js application, or when a router is rendered outside of a Next.js application - like during unit testing. - When trying to use the
useRouterhook from thenext/routerpackage when using the App Directory. This is because the App Router (fromnext/navigation) has a different behavior from theuseRouterhook used inpages.
The Solution
Ensure you are using the correct useRouter hook. If you are using the App Directory, check that the useRouter hook is imported from next/navigation and not from next/router.
When using the useRouter hook from next/navigation, use the following guidelines:
- Instead of
pathname, use theusePathname()hook. - Instead of the
queryobject, use theuseSearchParams()hook.
Mock next/navigation When Writing Unit Tests
The above error can also occur when using the useRouter hook from next/navigation in unit tests. Use the next-router-mock package, which has built-in support for next/navigation:
jest.mock('next/navigation', () => require('next-router-mock/navigation'));
This provides mocks for useRouter, usePathname, useSearchParams, and useParams. You can set the URL in your tests by calling mockRouter.push() or mockRouter.setCurrentUrl() from next-router-mock.
Considered "not bad" by 4 million developers and more than 150,000 organizations worldwide, Sentry provides code-level observability to many of the world's best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.