JJ Kasper

@dmythro @nextjs @timneutkens This was by design as standalone is separate from adapters and a post build step. Do you have specifics what you're trying to achieve with both together?

@nextjs Seems like `onBuildComplete` fires before standalone is ready, when I wanna do optimized standalone build. Is it by design @timneutkens?

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

@pranaygp @strehldev @TooTallNate Hi, just following up the latest workflows beta has a reworked integration that should have much better performance, please update and give it a try!

@strehldev @TooTallNate cc @_ijjk

@TooTallNate @pranaygp our dev setup seems to have gotten a bit more sluggish since I've added workflows. Any ideas what we could do to improve the performance on the next dev server?

@thehungrybird_ @pranaygp This is a common bug with Next.js config plugins not handling the config function version, left reply on the issue!

@pranaygp @_ijjk github.com/vercel/workflo…

was integrating workflows into an existing nextjs app and came across something curious. any idea why this happens, @pranaygp?

@peturgeorgievv @rauchg Hi, just following up the above PR has been merged. If you have a PR queued for updating the `GoogleAnalytics` script as well feel free to tag me and I can take a look at that as well!

@rauchg I think we need the exact same for: GoogleAnalytics - next/third-parties/google But I gotta say, you're doing the best marketing for Vercel as CEO. I have never seen a faster response from someone at the C level.

Are people using NextJS, not interested in Google Analytics? Why is this PR not merged? It's from half a year..., and it helps us use Google Tag Manager Gateway with the next library? Tag someone who might care please @rauchg github.com/vercel/next.js…

The incredible eng team behind workflow has sunk way many hours and brain cycles into this - @TooTallNate, @schniz,@_ijjk, @dillon_mulroy, @adriandlam_ and Peter Wielander Not to mention the much longer list of contributors across the company who helped bring this dream alive

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

@TooTallNate @ThePrimeagen I like to think I'm worth it 😉

@ThePrimeagen @_ijjk is this true?

is jj worth the jump? i am pretty use to git, but would am open to hear why jj is better

Next.js 15.5 • Turbopack for builds (beta) • Node.js middleware (stable) • TypeScript support improvements • `next lint` command deprecation • Next.js 16 deprecation warnings nextjs.org/blog/next-15-5

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

@Zenul_Abidin Here's recording youtube.com/watch?v=axfcwz…

@_ijjk Is there a youtube link of the replay so we can watch it again?

Excited to share our latest progress with adapters in Next.js! Join my talk to see how adapters can simplify deploying your apps everywhere 🚀

Worthy of applause: @nextjs will soon support adapters to deploy on any platform (@Cloudflare, @awscloud, etc.) Great talk by @_ijjk at @ReactSummit!

Next.js 15.3 • Turbopack for builds (alpha) • Community support for Rspack (experimental) • Client Instrumentation hook • Navigation hooks • TypeScript plugin improvements nextjs.org/15-3

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

@cramforce @stanzillaz Hi, I'm not able to verify any difference in behavior between those versions. Responded on the discussion here with further details #discussioncomment-11860017" target="_blank" rel="nofollow noopener">github.com/vercel/next.js…

@stanzillaz i'm surprised that it represents as a regression, because it appears intended behavior. Rational: If JS for a route 404s, then next guesses it might be because of skew and reloads to avoid that. This has "always" been the behavior. CC @_ijjk

Skew protection is such a good idea that we will spend the rest of the decade continuing to explore its implications and applications.

@rishi_raj_jain_ @diegohaz @leer ISR are static pages, they just also have the ability to revalidate on-demand via `revalidatePath` or similar. It won't incur serverless function usage unless you tell it to at runtime

@_ijjk @diegohaz I have a static page which I want to deploy on Vercel but it shows as ISR page always. There is no revalidate present. cc @leer

Is it possible to opt out from generating serverless functions (ISR) for every page on Vercel when using the Next.js App Router with server components? I tried dynamic = “error”/“force-static”, dynamicParams = false, everything. But it keeps generating ISR.

Next.js 15.1 • React 19 (stable) • Improved errors and source maps • `after` (stable) • `forbidden` / `unauthorized` (experimental) • CSS inlining (experimental) nextjs.org/15-1

@tanaken_dx 128kB was chosen as it's a fairly large size and we believe if you cross that you are most likely including more data than necessary which can slow down document loading

Could you please share the reasoning behind setting the threshold to 128kb? Thank you in advance, and I completely understand if you’re unable to respond due to your busy schedule.

@_ijjk Hi, I apologize for mentioning you out of the blue. If you’re busy, please feel free to ignore this message. I’ve been curious about why the threshold for the "Large Page Data" warning in Next.js is set at 128kb, so I opened the following discussion: