Framework
Reports that share this framework, grouped in one feed.
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.
During background revalidation of partially prerendered (PPR) routes, Next.js reads the Link header from the already-finished response object instead of from the values React passed to appendHeader, causing Flight-triggered regenerations to store no Link header and lose font preload hints.
In Next.js 16.3.5-16.4.0-canary.32, a redirect() inside a Suspense boundary in a layout triggers an instant navigation validation error on every warm request, although redirect is intentional control flow. This suppresses genuine blocking-prerender-dynamic findings on the same route.
In Next.js development mode, soft navigation to a route whose server component redirects after async work triggers an uncaught TypeError because React Server Components client code calls performance.measure with a negative end timestamp.
When using the browser back button to return to a page with a URL hash, Next.js erroneously scrolls to the anchor element, disregarding the preserved scroll position. This is caused by the Container component's componentDidUpdate triggering scrollToHash even on popstate navigations.
In Next.js dev with Turbopack, using next/dynamic to load a component that contains a plain import() causes the page HTML to reference a chunk that the dev server never emits, resulting in 404 errors on every page load. This affects both App Router (preload link) and Pages Router (script src). The actual dynamic import still works because the emitted loader chunk has a different hash.
Editing a server component before the page finishes hydrating triggers a React warning ('Can't perform a React state update on a component that hasn't mounted yet') and can lead to a hydration mismatch. The issue occurs only in Next.js dev mode with HMR active, both Turbopack and webpack.
The `next info` command incorrectly displays the latest stable version instead of the actual installed canary version, misleading users about their Next.js version.
In App Router-only builds, requesting a dynamic route with a malformed percent-encoded segment (e.g. /items/%E0%A4) triggers a DecodeError during route matching. Base-server attempts to render the Pages Router /_error page with a 400 status, but that page does not exist in builds without any Pages Router routes, resulting in a bare 500 response.
In Next.js 16.x, the image optimizer's fetchExternalImage rethrows raw fetch errors, causing a 500 Internal Server Error for upstream DNS failures, connection refusals, and TLS handshake errors. The expected behavior is a client-visible upstream error status (502), consistent with other upstream failure handling in the optimizer.
Using router.replace inside a Link's onClick handler before navigation causes the previous page to be skipped on back navigation on iOS 17+ and Chrome 127+ due to a WebKit history API race; workaround is to prevent default and sequence replace/push with a delay.
Next.js client bundles include unused constants from next/dist/shared/lib/constants.js and next/dist/lib/constants.js because client entrypoints resolve to CommonJS files, preventing Webpack/Turbopack from performing tree shaking. A user-provided webpack workaround redirects imports to ESM equivalents.
In Next.js dev with Turbopack, editing a file after client-side navigation does not trigger hot module replacement until a manual page reload. The HMR subscription for the new route is not registered after client navigation.
Next.js 16.3.8 with Turbopack shows a hydration error overlay when Cursor's built-in browser stamps data-cursor-ref attributes on DOM nodes. The attribute is not in server HTML or the React tree, so the mismatch is a false positive.
When building with bun --bun, Next.js logs a spurious error about usePathname outside Suspense for routes with fallback params, even though the component is inside Suspense. Root cause is an unhandled promise rejection in the aborted branch of makeHangingPromiseWithError, which Bun does not filter because AsyncLocalStorage context is missing in unhandledRejection listeners.
When navigating to a route that introduces a new nested layout, Next.js scrolls to the page segment instead of the top of the newly mounted layout, causing the layout's heading and intro content to be bypassed. This occurs because the scroll ref is only accumulated for leaf segments in render-tree.ts.
When using Incremental Static Generation (ISG) via `unstable_revalidate`, a custom `_app` component's `getInitialProps` may attempt to set response headers (e.g. Cache-Control) after the page response has already been sent. In production this triggers 'Cannot set headers after they are sent' errors or silently overrides the ISG page's cache headers, while development mode does not reproduce the issue.
Next.js metadata routes such as sitemap and robots are prerendered and respect revalidate, but their Cache-Control header is hardcoded to 'public, max-age=0, must-revalidate' instead of using s-maxage like other ISR routes. This prevents CDNs from caching these routes efficiently, especially in self-hosted environments.
When cacheComponents is enabled in Next.js 16.1.0-canary.16, dynamic routes that receive an already decoded percent sign (%) from a URL-encoded %25 trigger a 500 Internal Server Error due to invalid URI decoding during cache key generation.
Under Bun 1.4.2, Next.js 16.4.0 logs false 'unhandledRejection' errors for CLIENT_HOOK_DYNAMIC because the rejection filter relies solely on workUnitAsyncStorage.getStore(), which Bun does not restore in unhandledRejection listeners. This produces hundreds of build log errors despite successful builds and can hide real failures.
在 next start 使用文件系统缓存时，revalidateTag 立即过期标签后，由于写入过期时间使用 Date.now()（墙上时钟），而读取判断使用 performance.timeOrigin + performance.now()（单调时钟），两者存在进程启动时的几毫秒偏移，导致过期标签在短时间内仍被视为未过期，从而继续提供旧缓存页面。
Next.js 16.x with Turbopack and pnpm emits a false 'Module not found' warning for styled-jsx/style.js during Pages Router builds, even though the build succeeds and the file is traced.
Using styled-jsx in a Pages Router application with pnpm triggers a false 'Module not found' warning during Turbopack builds. The warning occurs because Turbopack's external tracing attempts to resolve styled-jsx/style.js from the project root, but pnpm's strict node_modules layout does not hoist styled-jsx to the root. The build still succeeds and the file is correctly traced via Next.js's own require hooks.