Next.js 15 features have fundamentally changed how production React apps get built, and the gap between teams using them well and teams fighting them is widening fast. Partial Prerendering, the stabilized App Router, Turbopack defaults, and the new caching model are not incremental changes — they are different mental models. If you are still treating Next.js like a glorified create-react-app, you are leaving performance, DX, and SEO wins on the table. Here is what actually matters in the current release and how to wield it without the footguns.
Table of Contents
Partial Prerendering Changes the Static vs Dynamic Debate
Partial Prerendering (PPR) is the headline Next.js 15 feature for a reason. Instead of forcing each route to be either static or dynamic, PPR lets you ship a static shell with dynamic holes that stream in. The login dropdown, the cart count, the personalized recommendations — they all live inside Suspense boundaries while the rest of the page hits CDN cache instantly.
The practical impact is huge for content sites with personalization. You stop choosing between SEO-friendly static pages and rich dynamic experiences. Read the official Partial Prerendering documentation before you sprinkle it everywhere — the mental model matters.
Server Actions Are Production-Ready Now
Server Actions hit stability in Next.js 14, but Next.js 15 cleaned up the rough edges around revalidation, error handling, and progressive enhancement. You can write a form handler that runs server-side, mutates your database, revalidates affected paths, and degrades gracefully without JavaScript — all in one function.
The win is not just less code. It is fewer API routes, fewer client-side state libraries, and fewer race conditions. If you are still writing `fetch(‘/api/…’)` from client components for mutations, you are doing it the old way. Pair Server Actions with the patterns from our API design best practices guide for clean boundaries.
Turbopack as the Default Dev Server
Turbopack stable for `next dev` means cold starts on a 500-component app dropped from 12 seconds to under 2 in our testing. HMR is near-instant. The build-side Turbopack is still stabilizing but the dev experience alone justifies upgrading.
The catch: a few webpack plugins you depended on may not have Turbopack equivalents yet. Check your custom loaders and Sentry/Datadog integrations before flipping the switch in CI. Vercel maintains a compatibility matrix on their blog that gets updated regularly.
The New Caching Defaults Are Saner
Next.js 14 cached aggressively by default and confused half the developer community. Next.js 15 flipped it: `fetch()` calls are uncached by default, `GET` route handlers are dynamic by default, and you opt into caching explicitly. This matches how most teams actually want to think about data.
If you are migrating, audit every `fetch` call and decide intentionally whether it should be cached. The `cache: ‘force-cache’` and `next: { revalidate: 60 }` options are now your explicit signals rather than implicit assumptions.
React 19 and the Use Hook
Next.js 15 ships with React 19 RC support, which means the `use()` hook for unwrapping promises in components, the new `useActionState` for form state, and the optimistic update hooks that make Server Actions feel instant. Combined with React Compiler (still experimental), a lot of the manual `useMemo` and `useCallback` ceremony goes away.
This is the part that requires the most retraining for senior React devs. The patterns you internalized over the past five years are not wrong, but they are no longer the best answer for most problems.
Wrap Up
Next.js 15 features reward teams willing to learn the new mental models — PPR, explicit caching, Server Actions, and React 19 idioms. If you are setting up a new project, start here. If you are migrating, do it route by route and lean on the codemods. The combination of web performance optimization techniques plus PPR is genuinely the best content delivery story available right now.
Frequently Asked Questions
Should I migrate an existing Next.js 14 app to 15 immediately?
For most teams, yes — but route by route. The caching default change is the biggest gotcha. Run your test suite, watch for unexpected SSR behavior, and use the official codemod before manually touching files.
Is Partial Prerendering production-ready?
PPR is stable for the experimental flag in Next.js 15 and used in production at Vercel and several large customers. It is safe for new projects but watch the changelog for edge case fixes.
Do Server Actions work without JavaScript enabled?
Yes, that is one of their main selling points. Forms degrade to standard HTML form submissions and progressive enhancement adds the optimistic UI when JS loads.
Will Turbopack break my existing build?
Turbopack is default for `next dev` only in 15. Production builds still use webpack unless you opt in. Most apps work without changes; custom webpack plugins are the main risk.
How does Next.js 15 compare to Remix or Astro?
Next.js wins for full-stack React apps with heavy personalization. Astro wins for content-first sites. Remix (now React Router 7) is closer to Next.js but with a different routing philosophy — neither is wrong.
