V16.4.0-Canary.12

Name: V16.4.0-Canary.12 bug reports
Creator: AI & Agent Dev Bug Sandbox

Reports that share this version, grouped in one feed.

Similar Reports

high95%

runtimeServerDeploymentId: prerendered flight payloads pin build-time deployment id causing infinite MPA reload loop

When runtimeServerDeploymentId is enabled and a build artifact is served under a different deployment ID, the navigation build ID embedded in prerendered flight payloads remains the build-time ID. This causes client-side skew detection (responseBuildId !== getNavigationBuildId()) to trigger an MPA fallback on every client navigation, resulting in an infinite hard-reload loop.

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

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

high85%

experimental.inlineCss duplicates global stylesheet 3x due to empty injectedCSS set in getGlobalErrorStyles

With experimental.inlineCss enabled, the full global stylesheet is embedded three times in every prerendered page: once in the SSR <style> tag, once in the RSC payload segment seed data (documented limitation), and a third time under the GlobalError entry because getGlobalErrorStyles passes a fresh empty Set as injectedCSS to createComponentStylesAndScripts, causing re-inlining of all root layout styles. This significantly inflates HTML size (e.g., ~1.3MB extra per page for a 435KB Tailwind sheet), increasing parse/memory cost and ISR write units.

V16.2.10 V16.3.3 V16.4.0-Canary.12 Next.js

high78%

Turbopack panics when node_modules symlink points outside project root in Git worktree

When using a Git worktree with node_modules symlinked to the primary checkout, running `next dev` with Turbopack triggers an internal panic: "Symlink node_modules could not be resolved: the symlink target leaves the filesystem root or its parent directory could not be resolved". The development server exits before serving the application. This affects parallel AI-assisted coding sessions that share dependencies across worktrees.

V16.4.0-Canary.12 Next.js

high85%

Turbopack first-wins module registration installs wrong factory for async loader with divergent bodies in different chunks

Turbopack emits the same async-loader module ID with different factories depending on chunk availability. The runtime's first-wins installation causes order-dependent behavior, leading to intermittent dynamic import failures: 'module factory is not available'.

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