Next.js 16.1 introduces Turbopack file system caching for development, a new bundle analyzer, and easier debugging in Node.js.

The Next.js Blog provides insights, updates, and tutorials on Next.js, a popular React framework for building server-side rendered (SSR) and static websites. Developers can learn about Next.js features, routing mechanisms, and data fetching strategies, as well as explore real-world examples and use cases of Next.js applications.

Next.js

Next.js 16.1 brings Turbopack file system caching to development mode by default, delivering up to 14× faster compile times when restarting the dev server. The release includes an experimental bundle analyzer for optimizing production bundles, simplified debugging with `next dev --inspect`, and improved handling of transitive external dependencies. Additional improvements include 20MB smaller installs, a new `next upgrade` command, and better async import bundling in Turbopack.

Next.js 16.1

Turbopack File System Caching for next dev

Improved Handling of serverExternalPackages

Before now, every nextjs update is welcomed with a high level of excitement, but now every nextjs update introduces a new level of fear and worry. We really need something very stable for a decent amount of time.

Hurray now I’m finally back on Turbopack with 16.1 and my build times are back down 🍻
Also it looks like they’re 25% faster than they used to be with prior versions of Turbopack.
V 16 has been a rocky start.

“use fixed everything in next update”

The wild part is that this sits just two columns away from even more vulnerabilities:
“Two new security vulnerabilities have been discovered in React Server Components: a high-severity Denial of Service (CVE-2025-55184) and a medium-severity Source Code Exposure (CVE-2025-55183). These affect React 19 (versions 19.0.0 through 19.2.1) and Next.js (versions 13.x through 16.x)”