Next.js Daily: Turbopack Optimizations and Runtime Improvements
The Next.js team merged 20 pull requests on February 11th, 2026, focusing on Turbopack performance optimizations, runtime code reorganization, and development tooling improvements. Key changes include removing deprecated CLI flags, adding text import support, and enhancing HMR infrastructure.
Duration: PT1M55S
Transcript
Good morning. This is Next.js Daily for February 11th, 2026.
The development team merged 20 pull requests with significant focus on Turbopack improvements and infrastructure changes.
Tim Neutkens merged the removal of turbopack and webpack flags from create-next-app, eliminating redundant CLI options since Turbopack is now the default bundler. Luke Sandberg added experimental support for importing files as text using the TC39 proposal syntax, gated behind the turbopackImportTypeText flag.
Tobias Koppers introduced the turbopackIgnoreIssue configuration option, allowing developers to suppress specific warnings and errors based on file patterns. This addresses the need to filter noisy warnings from third-party code without disabling all warnings.
Will Binns-Smith completed substantial runtime reorganization work, extracting core HMR client logic into shared runtime modules and adding server HMR infrastructure. These changes prepare the foundation for improved hot module replacement across different environments.
Sokra optimized Turbopack's persistence layer, adjusting block sizing constants to improve database access performance and reduce block count in the compacted database system.
Additional infrastructure improvements included trace timing enhancements for render path tracking and filesystem benchmark warning fixes that had been broken for six months.
The team also merged documentation corrections regarding React's use function, clarifying that it's not technically a hook, and updated test manifests for both development and production Rspack integration.
Several commits addressed flaky end-to-end deployment tests and devlow job timeouts that were causing build pipeline issues.
What's next: Server HMR implementation will continue with module factory replacement features, and the team will iterate on instant validation efficiency for client navigations.
That's your Next.js update for February 11th. Stay tuned tomorrow for more development news.