Affected version
Reports that share this version, grouped in one feed.
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 a Server Action is bound with .bind() inside a Client Component and used as a form action, submitting the form with JavaScript disabled leaves the browser pending indefinitely. The server executes the action, but the returned state is never rendered. Binding the action in a Server Component and passing it as a prop works correctly.
In Next.js 16.3.0 and later with optimisticRouting enabled by default, navigation from a dynamic segment to another dynamic route can fail to reset scroll position. This occurs when the app has a root parallel slot with a catch-all page returning null, alongside a sibling dynamic route. Predicted route trees reify stale params, causing a server mismatch and retry that consumes the scroll-ref on an empty catch-all leaf, so the new page retains the previous scroll offset.