From 4fdfca941cf451425e1722c21f207639db4ee874 Mon Sep 17 00:00:00 2001 From: JJ Kasper Date: Tue, 24 Sep 2024 17:11:42 -0700 Subject: [PATCH] Mention route field in app router migration (#70429) Closes: https://github.com/vercel/next.js/pull/59342 --- .../11-upgrading/04-app-router-migration.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/02-app/01-building-your-application/11-upgrading/04-app-router-migration.mdx b/docs/02-app/01-building-your-application/11-upgrading/04-app-router-migration.mdx index 2bfd0fa087ad4..98c6da98e32c9 100644 --- a/docs/02-app/01-building-your-application/11-upgrading/04-app-router-migration.mdx +++ b/docs/02-app/01-building-your-application/11-upgrading/04-app-router-migration.mdx @@ -474,6 +474,7 @@ In addition, the new `useRouter` hook has the following changes: - `basePath` has been removed. The alternative will not be part of `useRouter`. It has not yet been implemented. - `asPath` has been removed because the concept of `as` has been removed from the new router. - `isReady` has been removed because it is no longer necessary. During [static rendering](/docs/app/building-your-application/rendering/server-components#static-rendering-default), any component that uses the [`useSearchParams()`](/docs/app/api-reference/functions/use-search-params) hook will skip the prerendering step and instead be rendered on the client at runtime. +- `route` has been removed. `usePathname` or `useSelectedLayoutSegments()` provide an alternative. [View the `useRouter()` API reference](/docs/app/api-reference/functions/use-router).