Next.js: Server Action Fixes and Instant Insights Improvements

Transcript

Good morning, I'm your host with the Next.js development briefing for May 15th, 2026.

Seven pull requests were merged yesterday and today, led by significant infrastructure improvements. Hendrik Liebau merged a fix for server action forwarding loops with middleware rewrites. This resolves a critical issue where middleware rewrites would cause server actions to loop indefinitely, eventually timing out or crashing servers. The fix adds forwarding guards and proper error handling for unrecognized actions.

Josh Story contributed three pull requests focused on Instant Insights validation. The first improves error messaging by providing specific filenames for unvalidated boundaries in parallel route slots. The second ensures validation errors are only reported when the main development render is error-free, preventing duplicate error reporting. Story also removed the partialFallbacks configuration flag, which was already defaulted to true.

Aurora Scharff fixed a developer overlay bug where Date constructor calls were incorrectly labeled as Date.now() in sync IO error messages. The fix reorders API detection to prioritize more specific date constructor patterns.

Janka Uryga resolved an issue with cached navigations missing async API promises during dynamic rendering resumes, ensuring proper parameter resolution timing.

Finally, Jude Gao marked internal agent skills as hidden from external npx skills commands, cleaning up the public API surface.

What's next: The team continues working toward removing server-side action forwarding entirely in favor of client-side dispatching. Instant validation improvements are ongoing with focus on better error boundaries and developer messaging.

That's your Next.js briefing for May 15th. Back tomorrow with more updates.