Framework
Reports that share this framework, grouped in one feed.
Next.js build with Turbopack fails when encountering a named @container rule (e.g., @container scroll-content) that does not include a condition, because the bundled lightningcss version lacks support for named container queries (scroll-state). This causes 'Unexpected end of input' errors during CSS parsing, breaking builds for projects that rely on such CSS (e.g., nhsuk-frontend).
In Next.js production builds, when a Server Action writes a cookie and calls revalidatePath, and the page segment has an async layout and a loading.js boundary, the resulting transition can get stuck with suspendedLanes=512 and pingedLanes=0, causing the UI to never update. This is a stochastic bug affecting versions 16.2.x and 16.3.x.
When partial prerendering (PPR) is enabled, runtime-rendered pages with no postponed state are written to the file-system cache without an .rsc file, but the read path requires .rsc for such entries, leading to cache MISS on every request after eviction from memory.
router.refresh() unexpectedly scrolls the page to the top after a history.replaceState call changes the search params. The root cause is a hard-coded ScrollBehavior.Default in the tree-mismatch retry path (serverPatchReducer) and in the non-redirect server action path (serverActionReducer), which overrides the NoScroll intent of the original refresh.
Next.js does not pass identifierPrefix to React Flight renderer, causing useId() counters to reset per request and collide across client-side navigations when shared layouts persist.
In Next.js dev mode with output: export, dynamic routes with parameters requiring URL encoding (e.g., spaces) intermittently fail with a missing param error, while production builds work correctly. The bug depends on navigation order and is caused by inconsistent handling of encoded vs. decoded parameters.
Next.js SWC styled-components transform hoists the css prop to the styled component declaration, causing a ReferenceError due to temporal dead zone when the css prop references a const declared later in the module.
Next.js dev server calculates the V8 max-old-space-size based on host total memory (os.totalmem()), ignoring container memory constraints. In a Docker container with a memory limit, this sets an excessively high heap limit, potentially leading to out-of-memory (OOM) kills or performance degradation. Node.js already provides process.constrainedMemory() which respects cgroup limits; Next.js should use it when available.
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).
In Next.js 16.3.3 with cacheComponents enabled and a client component in the layout, the first request to a route with exactly 8 URL segments causes a RangeError (maximum call stack size exceeded) in React Flight's requireModule/getComponentNameFromType. The error disappears after any shallower route compiles or when using Node 22. This only affects dev mode (Turbopack or webpack).
Next.js Streaming Metadata renders a <div hidden> as the first child of <body>. React 19 hydration matches only by tag name and claims any prepended <div> (e.g. consent manager or chat widget) as the metadata wrapper. Hydration then fails with Minified React error #418, and React's clearContainerSparingly removes the third-party DOM node.
In Next.js 16.3.0 with Rspack enabled (NEXT_RSPACK=true) on Windows using pnpm, direct dependencies listed in transpilePackages are incorrectly externalized during development, leading to runtime errors such as 'No matching bindings found'. The issue is specific to the dev server and pages router; webpack dev and rspack production build work correctly.
After an ISR revalidation turns a route that was prerendered as a fully static redirect() into a partially prerendered page, client-side navigations fail: RSC requests receive the static shell only (or 404), never resume, causing React error 412 and a full page reload. The build-time prefetchDataRoute pins the route to serve prebuilt static RSC content, ignoring the new postponed cache entry.
When after() is called with a promise that never settles, the bookkeeping .then() callback registers in the caller's async context, pinning the entire request-scoped context (including RSC payloads) for the lifetime of the server process, leading to unbounded memory growth.
Next.js 16.3.5 production build using Turbopack panics with a TurbopackInternalError: 'expected chunkable module for async reference' when the bknd package is used. The webpack build succeeds, indicating a Turbopack-specific issue with async module chunking.
Next.js cacheComponents bfcache ordering causes React to reorder DOM siblings, re-parenting iframe subtrees and reloading them from the second visit onward.
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.
SearchParams aren't updated on client-side navigation when experimental cacheComponents and Draft Mode are both enabled; the page always shows the initial category until a hard reload. This is a caching key omission in Next.js App Router.
When using cacheComponents and partialPrefetching with a custom incremental cache that starts empty, the first request to a statically generated dynamic route (e.g., /en) results in HTTP 500 due to a NEXT_STATIC_GEN_BAILOUT error when Next.js attempts to render the fallback shell dynamically.
Next.js App Router with Edge SSR streaming defers metadata into Suspense chunks. Bots like TelegramBot, ChatGPT-User, GPTBot, and ClaudeBot terminate the response after the initial HTML chunk, causing empty social cards and missing SEO metadata.
In Next.js 16 with Turbopack, when a `next/dynamic` component is nested inside another `next/dynamic` component (both with `ssr: true` and CSS imports), the server-rendered HTML omits the `<link rel="stylesheet">` for the deeper component's CSS. This causes a flash of unstyled content (FOUC) and significant layout shift (CLS 0.4157) in production on slow connections. The issue is a regression introduced in 16.1.0 and persists through 16.4.0-canary.34. Webpack builds do not exhibit the problem.
Next.js 16.3.5 with reactCompiler and experimental.turbopackRustReactCompiler throws a runtime ReferenceError (Cannot access 'parseItem' before initialization) because React Compiler lowers hoisted function declarations to const bindings while leaving lazy useState initializers above them, breaking valid JavaScript hoisting.
Next.js build-time Instant Validation for Cache Components does not populate staged fallback params in the synthetic RequestStore, causing false negatives for invalid param access outside Suspense boundaries in dynamic routes with PPR.
Turbopack rejects SVG images that have a width attribute and a viewBox but no height, causing dev and build failures, while webpack handles the same SVG correctly by deriving height from the viewBox aspect ratio.
When using Router.replace or Router.push with a href that includes query parameters followed by a hash (e.g. /page?test=1#hash) and an as path that also includes the same hash, the getInitialProps method is not re-invoked on subsequent query changes. This breaks data fetching for masked-query patterns where query is hidden from the browser URL but hash must remain visible.
When a request receives a stale cached entry from a "use cache" function, the background revalidation incorrectly replaces the saved entry in the Resume Data Cache with the pending result of the regeneration. This leads to dev-time "uncached data" errors on validation renders and in production to runtime prefetch/RSC responses missing or mixing cache versions when using cacheComponents and partialPrefetching.
With App Router, dynamic pages using revalidate=0 or no-store fetch and a global loading.tsx get stuck on the loading fallback when JavaScript is disabled, making content invisible to crawlers and harming SEO.
Running `npm audit` on a project created with Next.js 15.5.23 reports high severity vulnerabilities from transitive dependencies `postcss` and `sharp`. The Next.js package pins outdated versions of these packages, requiring a dependency bump to secure patch releases.
Next.js 15 preloads all dynamic imports inside client components, causing both conditional chunks to be sent to the client, increasing initial JavaScript size and TBT compared to Next.js 14. The issue requires a user-land workaround until an upstream fix is released.
Setting `"type": "commonjs"` in a Next.js project using Turbopack causes build and dev failures because Turbopack enforces the declared module format on App Router source files (which are written as ESM) and on generated `.next-internal` server-action entries, even though Webpack ignores this field. The issue affects all App Router files and internal virtual modules, not just the `'use client'` proxy previously fixed.