Affected version
Reports that share this version, grouped in one feed.
In Next.js dev, when a prerendered page is activated while the HMR WebSocket is still in CONNECTING state, the client enters an infinite reconnect loop. This prevents page hydration and floods the server with repeated /_next/hmr upgrade requests.
Next.js dev server using rspack panics and aborts when error overlay or browser log forwarding requests original stack frames during a rebuild, due to stale compilation handle aliasing the in-progress compilation.
Next.js dev server retains ~90 MB per edit of a Server Component due to unbounded growth of Node's generatedSourceMapCache and React's fakeFunctionCache. Inline data URL source maps and line/column-dependent keys cause permanent cache entries, leading to OOM crashes.
In Route Handlers, calling cookies() inside after() returns the inbound cookie snapshot instead of the mutated values because the mutable cookie jar is not synchronized before after() switches the work unit phase.
The Edge Runtime process polyfill in Next.js defines process.getBuiltinModule as a throwing stub, violating Node's optional API contract. Packages such as js-bson that use feature detection (e.g., `if (globalThis.process?.getBuiltinModule)`) call the stub and trigger a runtime error, causing 500 errors in edge routes.
When using next/image with a relative src that returns a 302 redirect to an external image, the built-in image optimizer does not follow the redirect and returns a 500 Internal Server Error, while a native <img> displays correctly.