Affected version
Reports that share this version, grouped in one feed.
Next.js output: 'standalone' file tracing fails to include shared libraries loaded at runtime via dlopen by native addons, causing production crashes (e.g., sharp's libvips). Build succeeds silently; failure occurs only at runtime.
When using a nonce-based strict CSP, Next.js App Router fails to add the nonce attribute to the parser-inserted <script> tag for Suspense boundary chunks (loading.tsx, template.tsx, error.tsx). This causes the script to be blocked by 'strict-dynamic' on full page loads, leading to console violations and potentially broken client-side functionality.
When the stdout of `next dev` (Turbopack) is piped to a reader that exits early (e.g., `head -N`), subsequent requests hang forever and the process consumes CPU (~1.3 cores) in a native spin. The server stops responding while TCP connections are accepted but never answered.
Under plain HTTP/1.1 self-hosting, a burst of router prefetch (_rsc) requests occupies all six browser connections per origin; a Server Action submitted while prefetches are in flight is queued/aborted, leaving the UI frozen on stale props. Deterministic reproduction included.
sitemap.ts (and robots.ts) that export `revalidate` are incorrectly classified as STATIC_FILE in the adapter build output, losing their revalidate value and causing stale content on Vercel. The route is never regenerated and no function is emitted.
Next.js build tracing with webpack on Windows can fail when a traced dependency computes a home-rooted dynamic path. @vercel/nft then emits a glob whose base directory is the user profile, recursively walking Windows junction cycles (`Application Data` -> `AppData\Local`) and surfacing fatal `EACCES: permission denied, scandir` webpack errors.
When a navigation clicks a Link during an in-flight prefetch, a pending segment-cache entry is passed to React as a plain promise. In partial or rejected prefetches the promise resolves to null, causing React to commit an empty segment and drop the document title.
When a page calls notFound(), Next.js serves a minimal error shell (`__next_error__`) in the server HTML, omitting the root layout, `<html lang>` attribute, and the nearest not-found UI. This breaks accessibility, no-JS clients, and dynamic root layouts, and is inconsistent with the hydrated result. Affects App Router across multiple Next.js versions.