Next.js has become the dominant React framework for production web applications, and releases 15 and 16 have brought game-changing features. Partial Prerendering (PPR) blurs the line between static and dynamic rendering. Turbopack has gone stable, delivering 10× faster local builds. React 19 Server Actions are now production-ready. This guide covers every significant feature and the performance numbers behind the upgrade decisions.
Partial Prerendering: The Rendering Revolution
Partial Prerendering (PPR) is the most significant rendering advancement in Next.js history. It allows a single route to combine static shell delivery (instant from CDN) with streaming dynamic content — no need to choose between SSG and SSR.
- Static shell serves in <50ms from CDN edge nodes globally
- Dynamic Suspense boundaries stream in without blocking the shell
- Zero runtime cost for unchanged static regions on re-requests
- Enable with experimental.ppr = true in next.config.js
- Compatible with existing Suspense patterns — no migration needed
- Measured 40-60% improvement in LCP scores on content-heavy pages
Turbopack Stable: Local Dev Is Now 10× Faster
Turbopack, the Rust-based successor to webpack, is now the default bundler in Next.js 15+. The performance gains for large codebases are dramatic and compound over the development lifecycle.
- 10× faster initial server startup vs webpack on large codebases
- 700× faster HMR updates for most file changes
- Persistent caching across restarts eliminates cold-start penalty
- Native TypeScript and JSX processing without Babel overhead
- Stable module federation support for micro-frontend architectures
- Drop-in replacement — just run next dev (Turbopack is now the default)
React 19 Server Actions in Production
Server Actions remove the need for dedicated API routes for most form submissions and mutations. With progressive enhancement built-in, they work even without JavaScript, and the optimistic UI patterns make apps feel instant.
- Define server-side functions with "use server" directive inline or in separate files
- useFormStatus and useFormState hooks for pending/error states without useState
- useOptimistic hook for instant UI updates while mutations are in-flight
- Automatic CSRF protection — no manual token management required
- Works with any form element without JavaScript (progressive enhancement)
- Direct database calls from Server Actions — eliminate entire API layer for simple mutations
Caching Changes and fetch() Semantics
Next.js 15 reversed the aggressive default caching from v13/14 that confused many developers. Understanding the new caching model is critical for avoiding stale data bugs in production.
- fetch() is no longer cached by default — behavior matches native browser fetch
- Opt into caching explicitly with cache: "force-cache" or next.revalidate
- Route handlers and Client Components with cookies() are now dynamic by default
- unstable_cache replaces getStaticProps patterns for data caching in App Router
- use cache directive (experimental) for fine-grained component-level cache control
- Cache tags enable surgical revalidation without purging unrelated cached data
Conclusion
Next.js 15 and 16 represent a maturation of the App Router paradigm. The performance gains from Turbopack, PPR, and smarter caching defaults make upgrading a straightforward ROI decision for most teams. The migration path from the Pages Router is also well-documented now with codemods handling most of the heavy lifting. Sensussoft's web engineering team has migrated dozens of large Next.js applications to the latest versions. If you are planning an upgrade or building a new Next.js application, our team can architect and deliver a production-ready solution on the latest stack.
About Liam O'Brien
Liam O'Brien is a technology expert at Sensussoft with extensive experience in web development. They specialize in helping organizations leverage cutting-edge technologies to solve complex business challenges.
