Sign in

Next.js

@nextjs.org
11K followers 1 following 123 posts

The React Framework – created and maintained by @vercel.com

PostsRepliesMedia
Next.js @nextjs.org · 6h
Follow future Next.js security releases through our RSS feed: nextjs.org/feed/securi... Browse all security posts: nextjs.org/blog/tag/se...
000
Next.js @nextjs.org · 6h
We work with researchers through Vercel’s Open Source Bug Bounty to secure Next.js and other open source frameworks. To participate: hackerone.com/vercel
hackerone.com
Vercel - Bug Bounty Program | HackerOne
The Vercel Bug Bounty Program enlists the help of the hacker community at HackerOne to make Vercel more secure. HackerOne is the #1 hacker-powered security platform, helping organizations find and fix critical vulnerabilities before they can be criminally exploited.
220
Next.js @nextjs.org · 6h
Of the nine fixes announced last week, one critical and one high-severity fix were postponed due to upstream dependency delays. x.com/nextjs/stat...
120
Next.js @nextjs.org · 6h
The September Next.js security release is now available. It addresses seven vulnerabilities, including one high-severity issue. Upgrade now: ▲ ~/ npm install next@16.3.8 ▲ ~/ npm install next@15.5.27 nextjs.org/blog/septem...
nextjs.org
September 2026 Security Release
The September 2026 security release for Next.js is now available
173
Next.js @nextjs.org · 24/09/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
030
Next.js @nextjs.org · 24/09/2026
The Next.js September security release is planned for September 30, 2026. It will address nine vulnerabilities, including one critical and two high-severity issues, with fixes in 16.3.7 and 15.5.27. Upgrade once they are available. nextjs.org/blog/upcomi...
nextjs.org
Upcoming Next.js September Security Release
Next.js is preparing a scheduled September security release for September 30, 2026.
191
Next.js @nextjs.org · 22/09/2026
GPT-6 Sol debuts at 97% on Next.js evals, tying the highest success rate. Claude Opus 5.5 also reached 97%, joining Claude Fable 5.1. Opus ranks first among the three on average cost. View the leaderboard ↓ nextjs.org/evals
0140
Next.js @nextjs.org · 22/09/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
040
Next.js @nextjs.org · 22/09/2026
The September 22 out-of-band Next.js security update is now available. It addresses a critical upstream issue affecting Next.js 16. Next.js 15 is not affected, but 15.5.26 adds hardening. ▲ ~/ npm install next@16.3.6 ▲ ~/ npm install next@15.5.26 nextjs.org/blog/nextjs...
nextjs.org
Next.js Security Update for a Critical Upstream Issue
The September 22, 2026 out-of-band security update for Next.js is now available
1125
Next.js @nextjs.org · 22/09/2026
Grok 4.7 is the first @grok model to reach the top three on Next.js evals. View the leaderboard ↓ nextjs.org/evals
1101
Next.js @nextjs.org · 21/09/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
040
Next.js @nextjs.org · 21/09/2026
An out-of-band Next.js security update is planned for September 22, 2026. It addresses a critical issue in an upstream dependency. Upgrade to Next.js 16.3.6 or 15.5.26 as soon as they are available. nextjs.org/blog/upcomi...
nextjs.org
Upcoming Next.js Security Update for a Critical Upstream Issue
Next.js 16.3.6 and 15.5.26 are planned for a critical out-of-band security update on September 22, 2026.
2192
Next.js @nextjs.org · 04/09/2026
We closed 1,500 issues on 𝚟𝚎𝚛𝚌𝚎𝚕/𝚗𝚎𝚡𝚝.𝚓𝚜 in one month by building a 𝚌𝚕𝚘𝚜𝚊𝚋𝚒𝚕𝚒𝚝𝚢 agent with eve.dev. The workflow: 1. Search related work 2. Try to reproduce bugs across versions in a sandbox 3. Return context for review nextjs.org/blog/how-we...
nextjs.org
How we closed 1,500 GitHub issues in one month
How the Next.js team used an agent to research old reports and work through the issue backlog.
1183
Next.js @nextjs.org · 03/09/2026
Your Next.js app ships dozens of JavaScript chunks. Turbopack has to balance how many requests a page makes against how much code it ships. Learn how it works and what's new in Next.js 16.3. nextjs.org/blog/turbop...
nextjs.org
How Turbopack chunks your JavaScript
Turbopack’s chunking speeds up page loads and enables sharing code across pages. We shipped new experimental features to improve chunking in Next.js 16.3.
1191
Next.js @nextjs.org · 25/08/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
nextjs.org
Next.js by Vercel - The React Framework
Production grade React applications that scale. The world's leading companies use Next.js by Vercel to build static and dynamic websites and web applications.
040
Next.js @nextjs.org · 25/08/2026
The August Next.js security release is now available one day ahead of schedule to include a fix for a newly disclosed vulnerability in an upstream dependency. ▲ ~/ npm install next@16.3.3 ▲ ~/ npm install next@15.5.24 nextjs.org/blog/august...
nextjs.org
August 2026 Security Release
The August 2026 security release for Next.js is now available
1132
Next.js @nextjs.org · 25/08/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
nextjs.org
Next.js by Vercel - The React Framework
Production grade React applications that scale. The world's leading companies use Next.js by Vercel to build static and dynamic websites and web applications.
040
Next.js @nextjs.org · 25/08/2026
We’ve moved the scheduled August Next.js security release forward to today, August 25, to include a fix for an additional critical severity vulnerability. Next.js 16.3.3 and 15.5.24 will include fixes for both vulnerabilities. Upgrade once they are available. nextjs.org/blog/nextjs...
nextjs.org
Update: August Next.js Security Release
Next.js is moving the August security release forward to August 25, 2026.
1120
Next.js @nextjs.org · 20/08/2026
To stay up to date on future Next.js security releases, subscribe to our RSS feed: nextjs.org/feed/securi... Or browse all security posts: nextjs.org/blog/tag/se...
nextjs.org
Next.js by Vercel - The React Framework
Production grade React applications that scale. The world's leading companies use Next.js by Vercel to build static and dynamic websites and web applications.
050
Next.js @nextjs.org · 20/08/2026
In July, we began announcing Next.js security releases ahead of time. The next security release is planned for August 26, 2026. It will address one critical severity vulnerability with fixes in 16.3.2 and 15.5.24, so upgrade once they are available. nextjs.org/blog/upcomi...
nextjs.org
Upcoming Next.js August Security Release
Next.js is preparing a scheduled August security release for August 26, 2026.
2151
Next.js @nextjs.org · 18/08/2026
Instant Navigations in Next.js 16.3 lets you achieve snappy, app-like UX without giving up the benefits of Server Components. See how Cache Components and Partial Prefetching come together in a music player, social feed, calendar, and team chat. nextjs.org/blog/buildi...
nextjs.org
Building App-like Experiences with Next.js 16.3
Build app-like experiences with Instant Navigations, server-rendered data, optimistic updates, and live client state in Next.js 16.3.
1191
Next.js @nextjs.org · 07/08/2026
You can run the loop on your own app. Grab the Skill and prompt your agent with something like: "Make the navigation from /dashboard to /projects instant using the next-cache-components-optimizer Skill." www.skills.sh/vercel/next...
skills.sh
next-cache-components-optimizer — vercel/next.js
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side…
070
Next.js @nextjs.org · 07/08/2026
Navigations in v0 got ~3.5× faster with Next.js 16.3. An agent ran this loop on each slow nav: 1. Write a failing 𝚒𝚗𝚜𝚝𝚊𝚗𝚝() test 2. Apply a fix from the Skill 3. Re-run the test 4. Repeat 2–3 until it passes nextjs.org/blog/making...
nextjs.org
Making navigations instant in v0
The case study behind Instant Navigations in Next.js 16.3, and how we made v0's navigations instant using tests and a coding agent.
4211
Next.js @nextjs.org · 03/08/2026
When the network drops, requests normally throw. The experimental 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕.𝚞𝚜𝚎𝙾𝚏𝚏𝚕𝚒𝚗𝚎 flag keeps them pending and retries on reconnect. A companion 𝚞𝚜𝚎𝙾𝚏𝚏𝚕𝚒𝚗𝚎 hook reports when you're offline, so you can render some UI to let your users know.
Code snippet for an Offline Banner component in a web application, indicating user is offline and will retry on reconnection.
0130
Next.js @nextjs.org · 03/08/2026
The React Compiler optimizes your components at build time, letting you skip manual memoization. The React team built a Rust port of it, which we run in Turbopack instead of Babel. We tried this experimental version on v0: 34% faster to a ready page cold, 46% warm.
Code snippet configuring a React compiler in a Next.js project, highlighting settings for an experimental Rust port.
190
Next.js @nextjs.org · 03/08/2026
16.3 adds new first-party Skills that drive focused agent workflows. The 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙 Skill is general-purpose, letting an agent drive the browser and inspect the React tree to verify changes. Additional Skills are more specific, like adopting Cache Components.
Text details commands for an agent to manage browser interactions and optimize Next.js performance with specific skills.
130
Next.js @nextjs.org · 03/08/2026
The 𝚒𝚗𝚜𝚝𝚊𝚗𝚝() test helper asserts what content must be visible the moment you click a link. This prevents a later refactor from making the navigation slow again.
Code snippet for a test using Playwright to verify product visibility and inventory status upon navigation to a product page.
130
Next.js @nextjs.org · 03/08/2026
Prefetching only runs in production, which has made it hard to visually inspect your loading shells during development. The new Navigation Inspector pauses any navigation at the shell, so you can see which part of a route renders instantly, and which part waits on the network.
Navigation Inspector displays a paused debugger, showing a loading shell for the page at the target "/store/shoes" with navigation options.
180
Next.js @nextjs.org · 03/08/2026
Partial Prefetching gives you fine-grained control over how much content a link should prefetch for its target: a minimal loading shell, a partially rendered page, or all of its content. And loading shells can be reused across links, so users can never "beat the prefetch".
170
Next.js @nextjs.org · 03/08/2026
Instant Navigations is a new suite of opt-in tools and behaviors for SPA-like responsiveness in Next.js. First up: Instant Insights flags navigations that aren't instant, with a set of fixes for you (or your agent).
Next.js code snippet showing a navigation issue due to uncached data, with suggested fixes like Stream, Cache, and Block options.
180
Next.js @nextjs.org · 03/08/2026
Agents often code using outdated patterns from their training data. Now, 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 maintains an 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 block that points them to a local copy of the docs pinned to your app's version, ensuring they always use the latest best practices.
A text block outlines Next.js changes, emphasizing breaking updates, directory structures, and documentation access for developers.
280
Next.js @nextjs.org · 03/08/2026
Turbopack now supports the Vite-compatible 𝚒𝚖𝚙𝚘𝚛𝚝.𝚖𝚎𝚝𝚊.𝚐𝚕𝚘𝚋 API for loading multiple modules from the file system. For a Server Component that reads local files, like a folder of Markdown posts, it also brings hot-module reloading.
Code snippet implements a React function component to load and display Markdown posts using the Vite-compatible API.
170
Next.js @nextjs.org · 03/08/2026
React error boundaries used to swallow 𝚗𝚘𝚝𝙵𝚘𝚞𝚗𝚍 and 𝚛𝚎𝚍𝚒𝚛𝚎𝚌𝚝, and could only reset client state. Now 𝚌𝚊𝚝𝚌𝚑𝙴𝚛𝚛𝚘𝚛 defines a custom boundary that lets those pass through, and 𝚛𝚎𝚝𝚛𝚢() re-renders Server Components within the boundary.
Code snippet for a React error boundary with a fallback component, including error display and retry button functionality.
170
Next.js @nextjs.org · 03/08/2026
App Router rendering now uses native Node.js streams end-to-end, instead of converting to and from web streams on each request. With that overhead gone, apps handle up to 22% more requests under load in our benchmarks.
A bar graph shows performance comparison between web streams and Node.js streams, highlighting a 22% increase for Node.js under load.
1120
Next.js @nextjs.org · 03/08/2026
TypeScript 7 is a 10x faster native port of the compiler, and 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍 now uses it for type checking. Install it with 𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 -𝙳 𝚝𝚢𝚙𝚎𝚜𝚌𝚛𝚒𝚙𝚝@7.
Code snippet defines a Next.js configuration with experimental TypeScript CLI settings enabled.
2121
Next.js @nextjs.org · 03/08/2026
The disk cache that has sped up 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 since 16.1 now also works for 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍. Turbopack can read existing entries from .𝚗𝚎𝚡𝚝/𝚌𝚊𝚌𝚑𝚎 across CI runs before compiling new changes. We've seen projects build up to 5.5x faster on the warm path.
Bar chart comparing compile times for `next build` with cached and cold performances for nextjs.org, vercel.com/home, and vercel.com/geist.
180
Next.js @nextjs.org · 03/08/2026
Long 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 sessions now use up to 90% less memory. Turbopack used to keep visited routes cached in memory. With disk caching and memory eviction on by default, it can now offload that cache to disk.
Displays memory usage comparisons for two websites after compiling 50 routes, showing significant reductions in memory consumption.
1110
Next.js @nextjs.org · 03/08/2026
Next.js 16.3 is now available! • Up to 90% less memory in dev • Faster builds, type checking, and rendering • Better tooling for AI agents • Custom error boundaries • Instant Navigations for SPA-like responsiveness nextjs.org/blog/next-16-3 Here's what's new ↓
4767
Next.js @nextjs.org · 21/07/2026
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-2... x.com/nextjs/stat...
nextjs.org
July 2026 Security Releases
The July 2026 security releases for Next.js are now available
2153
Next.js @nextjs.org · 14/07/2026
Going forward, Next.js will be making security releases more predictable by announcing them ahead of time. More details: nextjs.org/blog/next-s...
nextjs.org
Next.js Security Release and Our Next Patch Release
Next.js is moving to a formal security release process
1255
Next.js @nextjs.org · 29/06/2026
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.
060
Next.js @nextjs.org · 29/06/2026
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.
Graph comparing Turbopack compile times for different scenarios, highlighting cold and cached durations for next build processes.
150
Next.js @nextjs.org · 29/06/2026
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.
Memory usage comparison after compiling 50 routes: Vercel.com drops from 21.5 GB to 2 GB; Next.js goes from 4,600 MB to 840 MB.
150
Next.js @nextjs.org · 29/06/2026
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-1...
nextjs.org
Turbopack: What's New in Next.js 16.3
Turbopack in Next.js 16.3 adds development memory eviction, persistent file cache for builds, experimental Rust React Compiler, and `import.meta.glob` support.
3314
Next.js @nextjs.org · 26/06/2026
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 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍.
040
Next.js @nextjs.org · 26/06/2026
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 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙.
140
Next.js @nextjs.org · 26/06/2026
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.
130
Next.js @nextjs.org · 26/06/2026
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.
130
Next.js @nextjs.org · 26/06/2026
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 𝚊𝚐𝚎𝚗𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛.
130
Next.js @nextjs.org · 26/06/2026
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-1...
nextjs.org
Next.js 16.3: AI Improvements
Actionable errors with paste-ready fix prompts, first-party Skills for the dev loop and Cache Components, and tooling that keeps coding agents in sync with your project.
5182