-
Notifications
You must be signed in to change notification settings - Fork 31.3k
Issues
is:issue state:open label:"Linking and Navigating"
is:issue state:open label:"Linking and Navigating"
Issue creation is restricted in this repository
Search results
Next.js v16 [Pages Router] (Regression) - Incorrect props fetched from
getServerSidePropsunder high parallel loadLinking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Pages RouterRelated to Pages Router.Related to Pages Router.Status: Open.scroll: falsenot preserved across async PPR retry navigations (force-dynamic pages)Dynamic RoutesRelated to dynamic routes.Related to dynamic routes.Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.ViewTransitions should work on popstate
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.Bug:
history.pushStateto a new URL reverts when route has a prefetched<Link>+proxy.tscookie-based redirectDynamic RoutesRelated to dynamic routes.Related to dynamic routes.Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.MiddlewareRelated to Next.js Middleware.Related to Next.js Middleware.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.router.replace with shallow: true persists shallow flag in history state, causing getServerSideProps to be skipped on browser back navigation
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Pages RouterRelated to Pages Router.Related to Pages Router.Status: Open.#93844 In vercel/next.js;Pages Router Turbopack route loader times out before page registration despite successful chunks
Internationalization (i18n)Related to Internationalization with Next.js.Related to Internationalization with Next.js.Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Pages RouterRelated to Pages Router.Related to Pages Router.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#93758 In vercel/next.js;router.refresh()eagerly refetches every in-viewport<Link>in v16 (was lazy in v15) — ~200x peak ISR Writes in productionLinking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.Status: Open.Router .push with fragments duplicates when doing client side navigation
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.#93126 In vercel/next.js;Pages Router hydration causes an extra client render on full page load when any rewrite is configured, including non-rewritten routes
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Pages RouterRelated to Pages Router.Related to Pages Router.Status: Open.[v16.2+] Router state header was sent but could not be parsed on soft navigation with dynamic rendering
CookiesRelated to the async cookies() function.Related to the async cookies() function.HeadersRelated to the async headers() function.Related to the async headers() function.linear: nextConfirmed issue that is tracked by the Next.js team.Confirmed issue that is tracked by the Next.js team.Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.Object.fromEntries(URLSearchParams) drops duplicate keys → stale UI on navigation
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.#92787 In vercel/next.js;Next 16.2 router cache issue, if search param name is used multiple times
linear: nextConfirmed issue that is tracked by the Next.js team.Confirmed issue that is tracked by the Next.js team.Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Status: Open.#92152 In vercel/next.js;