The React Framework – created and maintained by @vercel.

Pinned Tweet
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-in…
64
127
1,465
241,025
Building SPA-like experiences with Next.js With Instant Navigations, you can click around and the next page is there right away, the way a single-page app feels. The pages render on the server. Turning on 𝚌𝚊𝚌𝚑𝚎𝙲𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜 gives you an instant shell to prefetch, and 𝚙𝚊𝚛𝚝𝚒𝚊𝚕𝙿𝚛𝚎𝚏𝚎𝚝𝚌𝚑𝚒𝚗𝚐 prefetches that reusable shell per route before you click, with the dynamic parts streaming in after. Live demo, source code, and docs below ↓
14
24
275
24,394
We've added a security-only RSS feed so you can follow advisories and patches without watching the full changelog. Subscribe to stay up to date on future security releases. nextjs.org/feed/security.xml nextjs.org/blog/tag/security
Following our move to scheduled, pre-announced security updates, the July release is out. This release addresses several security issues in Next.js 16 and 15. Update to 16.2.11 (Active LTS) or 15.5.21 (Maintenance LTS) now. nextjs.org/blog/july-2026-se…
5
18
172
28,557
The latest Next.js 16.3 canary and preview releases are also patched. Update with: npm install next@16.3.0-canary.92 npm install next@16.3.0-preview.7 The stable 16.3.0 release will include the fixes as well.
2
7
47
7,610
Following our move to scheduled, pre-announced security updates, the July release is out. This release addresses several security issues in Next.js 16 and 15. Update to 16.2.11 (Active LTS) or 15.5.21 (Maintenance LTS) now. nextjs.org/blog/july-2026-se…
Going forward, Next.js will be making security releases more predictable by announcing them ahead of time. More details: nextjs.org/blog/next-securit…
6
17
272
79,953
Going forward, Next.js will be making security releases more predictable by announcing them ahead of time. More details: nextjs.org/blog/next-securit…
10
11
256
77,212
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.
1
1
56
8,478
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.
3
1
71
12,259
Coding agents, IDEs, typecheckers, and linters all run at dev time, and each one uses memory. Thanks to file-system persistence, Turbopack can now evict more of its in-memory cache. In Next.js 16.3, long dev sessions use up to 90% less memory.
1
3
112
13,993
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-tu…
46
103
1,154
365,797
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 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍.
1
17
4,412
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 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙.
2
19
6,878
The 𝚗𝚎𝚡𝚝-𝚌𝚊𝚌𝚑𝚎-𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜-𝚘𝚙𝚝𝚒𝚖𝚒𝚣𝚎𝚛 Skill grows a route's shell so more of the page is ready before the request lands. It builds on 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙, screenshotting each change and rolling back anything that didn't help.
1
7
1,350
The 𝚗𝚎𝚡𝚝-𝚌𝚊𝚌𝚑𝚎-𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜-𝚊𝚍𝚘𝚙𝚝𝚒𝚘𝚗 Skill migrates your app to Cache Components, feature by feature. It reads the Instant Insights, applies the fixes, and verifies each route with 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙, checking in so you stay in control.
1
2
41
6,875
We've retired our knowledge Skills. The auto-managed 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 teaches agents the framework's APIs now. We have new Skills that drive multi-step workflows instead. For example, 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙 verifies each change in a real browser via 𝚊𝚐𝚎𝚗𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛.
1
30
4,450
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-ai…
19
46
634
67,560
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.
2
5
154
22,138
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.
3
1
68
9,888
To guarantee instant navigations, the client must immediately render something when a link is clicked. Previously, Next.js tried to solve this by prefetching every link, a flurry of requests as you scrolled. Many of you told us this looked ridiculous, and frankly, we agree.
2
82
11,561
Instant Insights gives you options for how to make a navigation instant: • Stream the data behind a <𝚂𝚞𝚜𝚙𝚎𝚗𝚜𝚎> boundary • Cache the data with '𝚞𝚜𝚎 𝚌𝚊𝚌𝚑𝚎' Or allow the navigation to Block with 𝚎𝚡𝚙𝚘𝚛𝚝 𝚌𝚘𝚗𝚜𝚝 𝚒𝚗𝚜𝚝𝚊𝚗𝚝 = 𝚏𝚊𝚕𝚜𝚎.
3
1
114
32,043