Next.js Daily: Routing Performance and Build Optimizations
Next.js merged 20 pull requests focusing on router performance improvements, segment caching enhancements, and build process optimizations. Key changes include fixes for optional catch-all parameters, instant navigation improvements, and TypeScript build performance gains.
Duration: PT2M12S
Transcript
Good morning. This is Next.js Daily for February 26th, 2026.
The team merged several critical routing fixes yesterday. Andrew Clark merged a fix for optional catch-all parameters that weren't being properly tracked in the segment cache, which was causing incorrect content reuse across different parameter values. The solution uses a Proxy to intercept property access for missing parameters.
Hendrik Liebau merged cached navigations support, enabling instant display of cached segments on repeat visits to dynamic pages. The server now separates static and dynamic portions during rendering, with the client storing static segments for immediate display while fetching only dynamic data.
Janka Uryga fixed a bug where loading.js files weren't being recognized as suspense boundaries in instant validation. The fix moves boundary placement above LoadingBoundary components in the router hierarchy.
Andrew Clark also addressed server-patch retries that were incorrectly using replace navigation instead of preserving the original push or replace intent, which was breaking browser back button functionality.
On the build optimization front, Niklas Mischkulnig improved TypeScript performance by avoiding worker initialization when only doing config validation, reducing startup time from 85ms to under 5ms. Tim Neutkens fixed worker thread compatibility by sanitizing arguments to prevent DataCloneError exceptions.
Tobias Koppers replaced runtime mark_root calls with declarative function flags in Turbopack, moving aggregation number assignment to compile time. Benjamin Woodruff separated Turbopack compilation from the main build command, creating a new build-all option for full rebuilds.
Sebastian Silbermann updated error overlay snapshots to include error codes and removed deprecated test utilities to reduce maintenance overhead.
What's next: The team continues work on segment caching improvements and expects additional router performance enhancements. Build process optimizations remain a priority for faster development cycles.
That's your Next.js update for today. We'll be back tomorrow with more development news.