Next.js Daily: Turbopack Updates and Infrastructure Improvements
The Next.js team merged 14 pull requests focusing on Turbopack runtime improvements, CI test infrastructure fixes, and documentation updates. Key changes include memory optimization for persistent storage and configuration options for runtime backends.
Duration: PT1M47S
Transcript
Good morning. This is Next.js Daily for February 28th, 2026.
The team merged significant infrastructure improvements yesterday. Luke Sandberg merged a streaming SST writer for turbo-persistence, reducing memory usage from hundreds of megabytes to around 200KB per writer during large file operations. Benjamin Woodruff added runtime configuration options for Turbopack's node backend, allowing developers to swap between child processes and worker threads through experimental config settings.
JJ Kasper centralized test timings across CI workflows to fix shard divergence issues where some tests were missing entirely while others ran multiple times. The fix ensures consistent test distribution across all job groups by fetching timings once and sharing them via GitHub artifacts.
Will Binns-Smith restricted Turbopack's server HMR to app pages only, as API routes currently bypass the Turbopack runtime. The team also reverted the default loader runtime backend to child processes due to Node.js crashes, though this may change once newer Node versions address the underlying issues.
Documentation updates included fixes to the useReportWebVitals API reference, corrections to Docker example configurations, and the addition of Hostinger Web Apps Hosting as a deployment option. Joseph backported multiple documentation improvements to the 16.1.x branch.
Janka Uryga cleaned up the stream-ops codebase by removing unnecessary runInContext callbacks, simplifying the async context handling throughout the rendering pipeline.
What's next: The team continues optimizing Turbopack's runtime performance and may re-enable worker threads by default once Node.js stability issues are resolved. Infrastructure improvements should provide more reliable CI test execution.
That's your Next.js update for today.