Affected version
Reports that share this version, grouped in one feed.
In mixed App Router and Pages Router applications, Pages Router links to App Router routes trigger erroneous `_next/data` prefetch requests that return 404, and App Router links to Pages Router routes send RSC prefetch requests that receive HTML documents instead of Flight data.
When using parallel routes inside a route group, calling router.refresh() after a soft navigation can trigger a full-page reload instead of a soft refresh, causing loss of UI state and a broken user experience.
On the WASM SWC bindings, codeFrameColumns deserializes options directly into a strict CodeFrameOptions struct that cannot accept boolean color or undefined maxWidth, unlike the native N-API binding. This causes 100% of code frames to fail on the WASM fallback, replacing the actual error with a serialization error in the dev overlay, server console, and build diagnostics.
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.