Next.js

Next.js 16.3 Preview: Instant Navigations A new suite of tools that brings the responsiveness of client-driven SPAs to Next.js, without giving up what Server Components do best. The speed of the server, with the feel of the client. Try it and tell us what you think ↓ nextjs.org/blog/next-16-3…

React Compiler used to run as a Babel transform, which meant Turbopack spun up a Node.js worker and re-parsed every file. The React team's new Rust port drops that overhead. When enabled, Turbopack route compilation got 20 to 50% faster in tests on apps like v0.

Filesystem Cache has been speeding up 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 since 16.1, and now it works for 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍 too. By sharing the .𝚗𝚎𝚡𝚝 directory between CI runs, Turbopack can read existing entries from disk. We've seen builds run up to 5.5x faster on the warm path.

Turbopack: What's new in Next.js 16.3 Preview • Up to 90% less memory in dev • Up to 5.5x faster builds via Filesystem Cache • Faster HMR and dev startup • Experimental Rust React Compiler • 𝚒𝚖𝚙𝚘𝚛𝚝.𝚖𝚎𝚝𝚊.𝚐𝚕𝚘𝚋 support nextjs.org/blog/next-16-3…

Some agents never see the dev overlay. They don't drive a browser, and read errors from the terminal instead. So the same labeled fixes show up in the console too, during 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 and 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍.

Each fix on an Instant Insight comes with a prompt your agent can run end to end. It walks the agent through the whole flow: read the docs page for the patterns and trade-offs, apply the fix, then verify it in the browser with 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙.

Next.js 16.3 Preview: AI Improvements More and more Next.js is written by coding agents, so we're building a framework that helps them succeed. • Auto-managed 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 • First-party Skills • Agent Browser with React introspection • Actionable error messages nextjs.org/blog/next-16-3…

Instant Navigations builds on Cache Components. To migrate an existing app, install our Skill: npx skills add vercel/next.js --skill next-cache-components-adoption Then ask your agent to adopt Cache Components using the Skill.

So, we're borrowing a trick from single-page apps. Next.js now prefetches one reusable shell per route and caches it on the client, instead of a separate request per link. A click renders the prefetched shell instantly while the rest of the page streams in from the server.

Next.js 16.3 Preview: Instant Navigations A new suite of tools that brings the responsiveness of client-driven SPAs to Next.js, without giving up what Server Components do best. The speed of the server, with the feel of the client. Try it and tell us what you think ↓ nextjs.org/blog/next-16-3…

My React Summit talk is up: What RSCs Can Do in Next.js Today. To show it, I built a music player, open source and deployed on an early preview of Next.js 16.3. 🎵 next-beats.dev Watch the talk for the full walkthrough, and check the key patterns in code below ↓ gitnation.com/contents/what-…

Last night in London, we shared an early look at Instant Navigations and what’s coming in Next.js 16.3. Great conversations, sharp questions, and a lot of excitement for what’s next. Thanks to everyone who joined us. More to share soon.

The Next.js team is coming to San Francisco, Amsterdam, and London. • Instant Navigations with Next.js 16.3 • How we’re improving Next.js for AI Agents • Community hangout! nextjs.org/nights

We'll also have community lightning talks at Next.js Night Amsterdam: • @simeonGriggs Faster and cheaper with Cache Components • @farisaziz12 Teach your Next.js app how to take a punch

London: Thursday, June 18 luma.com/lfr946sc

Amsterdam: Thursday, June 11 Hosted alongside @reactsummit and @thejsnation conferences. Open to all, let's hang out! luma.com/34nqdfc3