Affected version
Reports that share this version, grouped in one feed.
Direct entry to a dynamic param route with a URL hash seeds the segment cache with a hashful canonical URL. Subsequent hashless router.replace/push calls then rebuild the target URL by appending an empty hash to the poisoned canonical URL, causing the browser to incorrectly retain the original hash. This breaks closing modals or any hash-keyed UI on deep links.
next/script strategy="beforeInteractive" inline scripts are serialized twice: once into the executable __next_s push in <head> and again into the React Server Components flight payload as client component props. The flight copy has no production reader, causing up to ~20 KB gzip overhead per pageview on real pages.
When Next.js standalone output is built with Turbopack (or webpack), output file tracing may fail to resolve a dependency but only records the failure in internal warnings that are never surfaced. The resulting .nft.json contains only the package.json of the broken dependency, so runtime require() fails with a deep internal module path. Build exits 0, leading to 500s or silently missing metadata in production.
Next.js 16.3.x type generation for `next/root-params` fails when an app has multiple root layouts, one of which is normalized to `/`. The generated `.next/types/root-params.d.ts` contains only `export {}` and the shipped ambient declaration resolves the module to `any`, silently bypassing strict TypeScript checks.