Jiwon Choi

@delba_oliveira 🖤🐐

Today was my last day at Vercel. It was a hard decision. Vercel was not just a job. It was ZEIT. My first app, first deployment, first open source contribution. The dream opportunity to work with Next.js. It was five years. Sweating over naming, mental models, progressive disclosure. Explaining, re-explaining, iterating. It was dozens of diagrams and videos, hundreds of docs, thousands of words, endless feedback. It was the tension between craft and speed. Hype, whiplash, and growth. It was for the web. I'm thankful to Vercel for letting me be part of its journey, as much as it was a part of mine 🖤

@jantimon @aurorascharff No its React error boundary under the hood. Are you facing any issue around it?

@devjiwonchoi @aurorascharff also during ssr?

𝚛𝚎𝚊𝚌𝚝-𝚎𝚛𝚛𝚘𝚛-𝚋𝚘𝚞𝚗𝚍𝚊𝚛𝚢 is great for declarative error handling, but it breaks with Server Components: it swallows 𝚗𝚘𝚝𝙵𝚘𝚞𝚗𝚍() and 𝚛𝚎𝚍𝚒𝚛𝚎𝚌𝚝(), and 𝚛𝚎𝚜𝚎𝚝() can't re-fetch server data. Next.js 16.2 𝚌𝚊𝚝𝚌𝚑𝙴𝚛𝚛𝚘𝚛: framework-aware, 𝚛𝚎𝚝𝚛𝚢() re-fetches RSC data, and internal errors propagate correctly. Blog post + demo in the thread ↓

@DcJai12 @jantimon @aurorascharff Just like typical error boundary it doesnt run in SSR. Are you facing any issue around it?

@devjiwonchoi @jantimon @aurorascharff @devjiwonchoi are there any gotchas regarding using it in pages router? it doesn't seem to work on SSR at certain times

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.

@okbel @cramforce @goncy 🐐🐐

Hire people you admire. Work with them. Learn from them. Ship great things. Repeat.

Next.js is for everyone

Adapters are now stable! A typed versioned description of the built Next.js application that platforms can use to deploy Next.js. We've also published how to run the Next.js test suite for platforms, allowing platforms teams to continuously run the latest Next.js test suite.

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

Turbopack: What's New in Next.js 16.2 • Up to ~375% faster updates with Server Fast Refresh • Improved Web Workers support • Subresource Integrity (SRI) support • Tree shaking for dynamic 𝚒𝚖𝚙𝚘𝚛𝚝() • 200+ bug fixes nextjs.org/blog/next-16-2…

Next.js 16.2: AI Improvements • Next.js-aware browser lets Agents improve your app • 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 included in 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙 by default • Browser errors forwarded to terminal • Dev server lock file prevents duplicate servers nextjs.org/blog/next-16-2…

@jantimon @aurorascharff Yeah it should be caught from the error boundary above

@devjiwonchoi @aurorascharff oh nice! thanks for letting us know - that’s a big step forward for ssr errors does catchError allow its fallback to rethrow errors?

@jantimon @aurorascharff Hey @jantimon! `unstable_catchError()` does work in Pages Router! Would love to hear your feedback on it. One thing to note is that `unstable_retry()` is unavailable, which depends on the App Router `router.refresh()` under the hood. github.com/vercel/next.js…

@aurorascharff could you please allow something similar for the pages router too? it would really help us to have better server side error boundaries not 100% sure about the best api design but here is a small poc example code: github.com/jantimon/nextj… vercel hosted: …tjs-ssr-error-boundary-poc.vercel.app

Two ways to handle a blocking component in Next.js: • Cache: so it can be prerendered with the rest of the page. • Stream: so the rest of the page doesn't have to wait for it.

can tap the screen to call dog over to you faster - dog has base speed (similar to irl) - each tap gives +1pts speed, exponentially decaying with each successive tap - speed decays over time (dog gets tired) - speed resets when reaching cursor

Git sync in v0 iOS

Next.js now logs Server Action execution including the amount of time the function took. Great work by @huozhi

one week ago we announced the redesign of the Vercel dashboard, and since then we’ve been busy addressing your feedback here are several things we’ve changed…

Is there any reason I shouldn't put the entire planning document into the commit message...? I'm already incentivized to keep it good so the context survives agent sessions. Might as well preserve it in the git history forever, right?