Watch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly. It's fixed in Chrome 150, but that won't land until the end of June.

I'm going on tour with the Next.js team in June! Coming to Amsterdam and London to share what's new in Next.js 16.3, hang out with the community, and answer your questions. Come say hi: • June 11: Amsterdam: luma.com/34nqdfc3 • June 18: London: luma.com/lfr946sc If you're in SF, there's one there too on June 9: luma.com/vercel-408x

We’ve released Next.js versions 16.2.6 and 15.5.18 with important security fixes. These fixes address multiple vulnerabilities across high, moderate, and low severity, including one upstream React issue. We strongly recommend upgrading as soon as possible. ⬇️

There's a cafe in Stockholm run entirely by Claude! I visited it. Field notes...

3 months ago I started building a coding agent that runs in the cloud. It's since written every line of code I've shipped, including itself. Today, I'm open sourcing it. Introducing Open Agents.

Next.js now has 37 million weekly downloads. 2.5x more than 6 months ago. Usage is accelerating. Excited to keep supporting the millions of applications being built on Next.js!

Vercel Sandboxes are now the fastest sandbox using real VMs as security boundary based on the @computesdk benchmark. The team has been absolutely cooking on this. And the best thing: Because we have a unified Fluid Compute stack across Sandbox, Builds, and Functions these wins are often shared across the stack. On the feature side there is a really exciting roadmap ahead as well. My favorites (all driven by feature requests from our customers): - Persistent sandboxes (in beta, GA immanent) - The fully mutable firewall also becomes fully programmable

New agent skill: 𝚛𝚎𝚊𝚌𝚝-𝚟𝚒𝚎𝚠-𝚝𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗𝚜 Add React <𝚅𝚒𝚎𝚠𝚃𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗> animations to any React app. Also covers how Next.js can natively integrate them. • Animate elements across navigations • Slide pages forward and back • Smooth loading transitions • Composition and accessibility handled

To quote from my keynote at Vercel's internal offsite: Software is free as in puppies. It will pee in your bedroom and eat your furniture. The weight of every line of code is real. We will need to maintain it. We will need to port it. It goes into the context window. And somebody in this room will get paged at 2am because it did something unexpected

The Vercel security and compute teams have conducted an investigation into the malicious takeover of the 𝚊𝚡𝚒𝚘𝚜@𝟷.𝟷𝟺.𝟷 npm package. • We’ve blocked outgoing access from our build infrastructure to the Command & Control hostname 𝚜𝚏𝚛𝚌𝚕𝚊𝚔.𝚌𝚘𝚖. • The malicious version of the package has been blocked and unpublished from npm. • Vercel’s own infrastructure and applications have been unaffected. • We recommend checking your supply chain for exposure. For more information, read the full advisory ↓ vercel.com/changelog/axios-p…

Big day! We are introducing the Next.js Adapter API 🎉

Next.js 16.2 introduces a stable Adapter API, built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud. But the API is only part of the story. Next.js is used by millions of developers across every major cloud, and making it work well everywhere is on us. Here are our commitments. nextjs.org/nextjs-across-pla…

Gave the experimental 𝚗𝚎𝚡𝚝/𝚛𝚘𝚘𝚝-𝚙𝚊𝚛𝚊𝚖𝚜 inside "use cache" a spin with next-intl in Next.js 16.2. Cached components can read locale directly instead of prop-drilling it from the page. Updated my blog post with what I found ↓ aurorascharff.no/posts/imple…

View Transitions just got simpler with Next.js 16.2. <𝙻𝚒𝚗𝚔> now has a 𝚝𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗𝚃𝚢𝚙𝚎𝚜 prop. Tag your navigation with a type, and <𝚅𝚒𝚎𝚠𝚃𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗> picks the right animation.

Next.js 16.2 • Up to ~60% faster rendering • Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup • Server Function 𝚍𝚎𝚟 logging • Redesigned error page • Better hydration errors • 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay nextjs.org/blog/next-16-2

When Cloudflare says "94% test coverage" - it's important to understand what that actually means. Their own readme says "94% of the API has full or partial support" (load-bearing "partial" here). In other words, this does not mean that they're actually testing 94% of the Next.js entire test suite (13,708 tests cases). "94% of the API surface" means they wrote a 52-item checklist and gave themselves a score. This is "we have a function with that name."... It's a cherry-picked vanity metric. That checklist hides what's actually broken. Take parallel routes: vinext tests 15 server-render cases. We test 90 across 27 directories, because the hard part is client-side (slot state retention, catch-all specificity, scoped revalidation, back/forward history). None of which vinext implements. It just straight up does not work. We've found this pattern across the feature surface. On the real Next.js test suite: 13% dev, 20% e2e, 10% production. They can evidently throw an agent at this, but it's a good reminder that if you don't understand what you're building in the first place, you're going to have a hard time. Does the team shipping this actually understand what they've built? If you're parading "94% coverage" to the world and features are fundamentally broken past the happy path, either you know and you're being deliberately misleading, or you don't know, which is scary.

punching holes in a static next.js shell to create "dynamic islands" with cache component joelclaw.com/cache-component…

We are also working on a way to enable this experience for existing projects as long as they are on the Canary version that supports it.

Next.js installs will soon include version-matched docs, giving agents context on new and recently updated APIs. In our evals, this improved success rates by ~20%. Try it out: 𝚗𝚙𝚡 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙@𝚌𝚊𝚗𝚊𝚛𝚢

As more Next.js apps are built with AI, we've been focusing on improving the agent experience. Here's what we've learned, and how we're thinking about agents as first-class users ↓ nextjs.org/blog/agentic-futu…