Next.js 16.1 focuses on faster development workflows and improved stability, with major updates to Turbopack and tooling.
Turbopack file system caching for next dev is now stable and on by default. Compiler artifacts are stored on disk, leading to significantly faster compile times when restarting your development server, especially in large projects.
Internal applications at Vercel have been dogfooding this for the past year. To learn more about how we built file system caching for Turbopack, watch Luke Sandberg's talk at Next.js Conf .
Following this release, we'll be stabilizing file system caching for next build . See our documentation for more information, and share your feedback on the dedicated GitHub discussion.
This is an excerpt. The full article is published by Next.js Blog.
Continue reading at Next.js Blog