useRouter
API reference for the useRouter hook.
The useRouter hook allows you to programmatically change routes inside Client Components.
Recommendation: Use the <Link> component for navigation unless you have a specific requirement for using useRouter.
useRouter()
router.push(href: string, { scroll: boolean }): Perform a client-side navigation to the provided route. Adds a new entry into the browser's history stack.router.replace(href: string, { scroll: boolean }): Perform a client-side navigation to the provided route without adding a new entry into the browser’s history stack.router.refresh(): Refresh the current route. Making a new request to the server, re-fetching data requests, and re-rendering Server Components. The client will merge the updated React Server Component payload without losing unaffected client-side React (e.g.useState) or browser state (e.g. scroll position).router.prefetch(href: string, options?: { onInvalidate?: () => void }): Prefetch the provided route for faster client-side transitions. The optionalonInvalidatecallback is called when the prefetched data becomes stale.router.back(): Navigate back to the previous route in the browser’s history stack.router.forward(): Navigate forwards to the next page in the browser’s history stack.
Good to know:
- You must not send untrusted or unsanitized URLs to
router.pushorrouter.replace, as this can open your site to cross-site scripting (XSS) vulnerabilities. For example,javascript:URLs sent torouter.pushorrouter.replacewill be executed in the context of your page. - The
<Link>component automatically prefetch routes as they become visible in the viewport. refresh()could re-produce the same result if fetch requests are cached. Other Dynamic APIs likecookiesandheaderscould also change the response.- The
onInvalidatecallback is called at most once per prefetch request. It signals when you may want to trigger a new prefetch for updated route data.
Migrating from next/router
- The
useRouterhook should be imported fromnext/navigationand notnext/routerwhen using the App Router - The
pathnamestring has been removed and is replaced byusePathname() - The
queryobject has been removed and is replaced byuseSearchParams() router.eventshas been replaced. See below.
View the full migration guide.
Examples
Router events
You can listen for page changes by composing other Client Component hooks like usePathname and useSearchParams.
Which can be imported into a layout.
Good to know: <NavigationEvents> is wrapped in a Suspense boundary becauseuseSearchParams() causes client-side rendering up to the closest Suspense boundary during static rendering. Learn more.
Disabling scroll to top
By default, Next.js will scroll to the top of the page when navigating to a new route. You can disable this behavior by passing scroll: false to router.push() or router.replace().
Version History
| Version | Changes |
|---|---|
v15.4.0 | Optional onInvalidate callback for router.prefetch introduced |
v13.0.0 | useRouter from next/navigation introduced. |