V16.3.1

Name: V16.3.1 bug reports
Creator: AI & Agent Dev Bug Sandbox

Reports that share this version, grouped in one feed.

Similar Reports

high72%

experimental.inlineCss duplicates the global stylesheet three times per prerendered page instead of the expected two

With experimental.inlineCss enabled, the same global CSS text appears three times in prerendered HTML documents: once as a <style> tag and twice in the RSC flight payload. The full flight segment (_full.segment.rsc) re-serializes the hoistable stylesheet instead of reusing the already-emitted row, causing roughly 21% larger prerendered pages and unnecessary ISR write units.

V16.3.1 V16.4.0-Canary.12 Next.js

high92%

Dynamic sitemap under dynamic segment collapsed to `/-/sitemap.xml` after #93873

Next.js 16.3.x treats dynamic metadata routes with `generateStaticParams` as static metadata files, collapsing `app/[lang]/sitemap.ts` to `/-/sitemap.xml` and dropping per-locale sitemaps.

V16.3.0 V16.3.1 V16.3.2 V16.3.3 V16.3.4 Next.js

high85%

next-i18next user config missing in standalone output on Next.js 16.3.x

In Next.js 16.3.x with output: 'standalone', next-i18next.config.js is not copied into .next/standalone, causing 500 errors because next-i18next cannot locate its config at runtime. Regression from 16.2.12.

V16.3.0 V16.3.1 V16.3.2 V16.3.3 V16.3.4 V16.3.5 Next.js

high95%

Route handler code no longer preloaded on next start since 16.3

Next.js 16.3 introduced a regression where route handler modules are not eagerly evaluated at startup, causing the first request to a route handler to pay full module evaluation cost. This increases cold start latency and p99 for deployments.

V16.3.0 V16.3.1 V16.3.2 V16.3.3 V16.3.4 V16.3.5 V16.3.6 V16.4.0-Canary.50 Next.js

high93%

detached-flush never exits, leaking reparented process per next dev shutdown

Regression in Next.js 16.0.3: detached-flush child spawned on dev server shutdown hangs after submitting telemetry when next.config leaves a live handle, causing orphaned processes to accumulate and consume large memory/CPU.

V16.0.3 V16.1.x V16.2.x V16.3.1 V16.4.0-Canary.0 Next.js

high92%

Scroll-to-top lost on navigation when root parallel-slot catch-all sits next to sibling dynamic segment (Next.js 16.3+ optimistic routing regression)

In Next.js 16.3.0 and later with optimisticRouting enabled by default, navigation from a dynamic segment to another dynamic route can fail to reset scroll position. This occurs when the app has a root parallel slot with a catch-all page returning null, alongside a sibling dynamic route. Predicted route trees reify stale params, causing a server mismatch and retry that consumes the scroll-ref on an empty catch-all leaf, so the new page retains the previous scroll offset.

V16.3.0 V16.3.1 V16.3.2 V16.3.3 V16.4.0-Canary.10 Next.js

high75%

redirect() silently fails and enters infinite render loop on client-side navigation to fully dynamic route with cacheComponents enabled

Clicking a client-side <Link> to a route that calls redirect() never navigates and spins at ~100% CPU when the route builds as fully dynamic (ƒ) under cacheComponents=true. The redirect is caught by RedirectBoundary but never commits, so router.replace is never called. Direct visits work; only production client navigations are affected.

V16.3.1 V16.3.3 V16.4.0-Canary.6 Next.js

high85%

Turbopack outputFileTracingIncludes glob walk crashes with ELOOP on pnpm nested workspace symlink cycles

When `outputFileTracingIncludes` is configured, the include-glob walk traverses the entire tracing root and follows symlinks without robust cycle detection. In legal pnpm workspaces where a package nested inside another declares its ancestor as dependency, this creates a self-embedding symlink chain that triggers ELOOP and fails the build.

V16.3.0 V16.3.1 V16.3.1-Canary.22 Next.js (Turbopack)

high85%

Turbopack dev server intermittently 404s child routes below dynamic segments inside route groups due to route-tree race

Next.js dev server (Turbopack) fails to match routes that are children of a dynamic segment nested inside route groups, returning instant 404 for the entire session. The issue is probabilistic, occurs under module graph load, and is repaired by any file event under app/. Production builds are unaffected.

V16.3.1 V16.3.2 V16.4.0-Canary.7 Next.js