Next.js 15 & React 19: What Every Developer Needs to Know Right Now

use() Hook

The new `use()` hook lets you read promises and context inside render — including async operations — without the ceremony of useEffect + useState.

Next.js 15: What's New

Partial Prerendering (PPR) — Now Stable

PPR is the killer feature. A single route can have a static shell (served instantly from CDN) with dynamic holes that stream in. A product page can show the layout, navigation, and static sections from cache while the personalised pricing and stock data stream in from the server. Best of both worlds.

Turbopack for Production

Next.js 15 ships with Turbopack stable for both dev and production builds. Build times for large apps have dropped 60-80% compared to webpack.

after() API

New `after()` function lets you run code after a response is sent — perfect for analytics, cache invalidation, and logging without delaying the user response.

Improved Caching Defaults

Next.js 14's aggressive caching caused confusion. In 15, fetch requests and route handlers are no longer cached by default — much more predictable behaviour.

Migration Tips

1. 1Upgrade Next.js with `npx @next/codemod@canary upgrade latest` — it auto-fixes many breaking changes
2. 2Review any fetch() calls with revalidate options — caching defaults changed
3. 3Test Turbopack in dev first — a few webpack-specific plugins need alternatives
4. 4RSC + Server Actions can replace most of your API routes for data mutations

The stack is maturing fast. If you're starting a new project in 2025, Next.js 15 with React 19 is the clear choice.