Affected version
Reports that share this version, grouped in one feed.
A client disconnecting during /_next/image optimization causes the response generator promise to never settle, permanently poisoning the cache key for all subsequent requests on self-hosted Next.js (next start/standalone).
Next.js 16.4.0-canary.22 with Turbopack and experimental cacheComponents reports a dev validation error when a page uses a dynamic import for a client component. The page renders but the validation worker fails with 'module factory is unavailable'. Static imports or disabling devValidationWorker resolve the issue.
When using dynamic(..., { ssr: false }) in the Pages Router, if a sibling Suspense boundary throws during hydration and React retries after the dynamic import has resolved, the loader's useSyncExternalStore uses the current loaded state as the server snapshot. This causes React to see a mismatch between the server-rendered loading state and the now-loaded client state, discarding the server-rendered DOM and falling back to client rendering.
Client-side next/form string actions append FormData entries to URLSearchParams without normalizing line endings according to the HTML specification, causing LF-only line breaks instead of CRLF.