Zack Tanner

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…

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-…

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

Mass-generating PRs with your agents and clawbots isn't helping open source. It's quietly burning out the people who actually maintain it. Please stop.

i'm looking for someone truly obsessed with web performance to join the Next.js team no need for prior framework experience, just strong React skills and real product performance wins :) if you love squeezing every millisecond out of the web, please reach out 🙏

@samducker @rauchg Hey @samducker! It sounds like Cache Components + 'use cache' is what you're looking for: nextjs.org/docs/app/getti… Wherever you're fetching your CMS data, you can tag that with 'use cache'. This will signal Next.js to cache that data at build time as part of the static HTML.

@rauchg Is there a Next.js (App Router) equivalent to TanStack Start’s “Static Server Functions” (run at build, cache to static JSON, fetch at runtime, but not have to entirely build the page as static)? Use case: proxy headless CMS content into a local JSON file as opposed to having to request it every time tanstack.com/start/latest/d…

Next.js 16 • Cache Components • Turbopack enabled by default • Turbopack file system caching (beta) • Optimized navigations and prefetching • Improved caching APIs • Build Adapters API (alpha) • React 19.2 nextjs.org/blog/next-16

@pablostanley @vercel @v0 @evilrabbit_ Together again ❤️

joining the super talented team at @vercel as a designer. working on @v0 and the next gen of creative tools

Next.js 15.4 • Turbopack Builds: 100% integration test compatibility for next build --turbopack • General stability and performance improvements • A preview of what's coming in Next 16 nextjs.org/blog/next-15-4

soon in @nextjs, browser errors & logs can show in your terminal for your AI to read

@cramforce @peer_rich @rauchg Yeah, PRs for font updates is currently automated though we still manually review + merge. Looks like the Cal Sans update is on deck! github.com/vercel/next.js…

@peer_rich @rauchg Yeah, but I don't know how exactly that works. It likely just works the next time we release @zt1072

does import { CalSans } from next/font/google need an update? @rauchg

@reactreaper 👋🏻 I’ve opened DMs, though the preferred disclosure for any potential security issues is outlined in our readme — github.com/vercel/next.js… and click the "Report a vulnerability" button.

Hey @zt1072 , i have a high security issue in Nextjs on some major sites. I can't DM you unfortunately, and can't publish it publicly. Pls DM.

Next.js 15.2 • Redesigned Error UI & Improved Stack Traces • Streaming Metadata • Turbopack Performance Improvements • View Transitions (experimental) • Node.js Middleware (experimental) nextjs.org/blog/next-15-2

@trashh_dev @wesbos hahaha why do I look so upset

@wesbos @zt1072 wanted to fix it

When you have been shit posting all day and have to get some work done

@tebayoso @vercel This is supposed to fail the build in Next.js. We'll look into it, thanks for the report!

@borisfyi Make sure you add a `default.tsx` in your left/right slots. When loading a route that has a parallel route with no matched slot, it'll be a 404 error. nextjs.org/docs/app/api-r… Forked sandbox: codesandbox.io/p/devbox/paral…

@zt1072 Right! I shouldn't have tested with interception routes, it was irrelevant. As I tried to say in my last tweet, I also tried with `app/@left/delete/page.tsx` but without success. Screenshot from the updated sandbox:

Hey @zt1072 👋 I know you worked on parallel routes some time ago. Is this expected? codesandbox.io/p/devbox/paral… The same thing happens with (.)delete. I don't know if it is relevant, but it is used in this example: #modals" target="_blank" rel="nofollow noopener">nextjs.org/docs/app/build…

@borisfyi The (.)delete syntax (aka the interception route) will be shown on soft navigation, but not if you refresh the page or go directly to the URL. In those cases, it'll look for `app/delete/page.js`, and if it can't find one, it's meant to be treated as a 404 error.

@zt1072 I was trying to render: "This is the delete page". Which happens correctly when navigating using Link, but not when loading/reloading the page from /delete directly. I tried with both a regular route and and interception route. I changed it from the sandbox: (.)delete/ => delete/

@huozhi Something like this 🤣 youtube.com/watch?v=RCHT6g…

I’m really curious about the working conditions of people who are being tagged infinitely everyday, and having a bunch of working messages to reply. How’s their day like and how to keep it going 👀

Next.js 15 RC ◆ React 19 + React Compiler support ◆ `fetch` and Route Handlers no longer cached by default ◆ Incrementally adopt Partial Prerendering ◆ New `create-next-app` design ◆ next/after (Experimental) nextjs.org/15-rc