Joseph Chamochumbi

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

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 ↓ #update-nextroot-params-is-here-nextjs-162" target="_blank" rel="nofollow noopener">aurorascharff.no/posts/implemen…

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.

@peteralexbizjak The change log is up now though. github.com/vercel/next.js…

@icyJoseph_dev Oof... Alrighty then, never mind.

How is Next.js 16.2 out already, but I can't find a release on GitHub, or any changelog?

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

@costiniuc00 @aurorascharff @delba_oliveira @timneutkens Yeah - late to the party here - but you probably saw it in the docs, under the snippet you linked, 𝚞𝚜𝚎T𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗 is the way... - #nested-error-boundaries" target="_blank" rel="nofollow noopener">nextjs.org/docs/app/getti…

@aurorascharff @delba_oliveira @timneutkens or some recommended approach outside of transitions would be great

Is there any work happening to resolve this issue of code duplication? Basically we can handle render-time errors with 𝚎𝚛𝚛𝚘𝚛.𝚝𝚜𝚡. Meanwhile we have such error handling per component for errors inside event handlers. @aurorascharff , @delba_oliveira , @timneutkens

@wesbos and to wrap up, I guess you can infer from here, that... the tags, p, button, etc, are, well, Client Components -ish...

feels good to have obscure react knowledge again 🔙🔛🔝

Some guy on reddit figured out that you can now use DOM events like onClick onHover _in a react server component_ no client component required I can't find any docs on this. When was this introduced? Confirmed it works on my Waku site

@wesbos And that, the happy path we've been trying to present, is via transitions, so you can have the isPending indicator, and leverage the so called async React.

@wesbos I know I am overreaching here, but in the Next.js docs there's one example, with an inline server function, being passed to a form action prop, all in the same server component.

@JamieBytebender @nextjs Are you using canary though? There are instructions there for pre/post v16.2.0-canary.37

Are these docs correct @nextjs nextjs.org/docs/app/guide… ? There's no node_modules/next/dist/docs/ on default installation

@hunvreus @Lawrence_sticks Appreciate it. A lot of perf upgrades have happened since the last minor release. For testing sake, it is also worth trying w/ canary. There are a lot of perf upgrades landing on the next release.

@icyJoseph_dev @Lawrence_sticks Pretty slammed, but I'll try and get something to you guys asap.

Main issues with Next.js: 1. Turbopack is slow and buggy. 2. RSC, and the overall push for server-side rendering, blows. The dev server regularly hangs for 10+ seconds or stops working, especially if you make a lot of changes at once (agents, anybody?). Use Vite and TanStack.

@hunvreus @Lawrence_sticks Any chance we could get a hold of a trace? #turbopack-tracing" target="_blank" rel="nofollow noopener">nextjs.org/docs/app/guide…

@Lawrence_sticks My issue is the developer experience. It’s just a PITA to develop with it.

@infinterenders @jacobmparis Isn't it like, a use case for the value passed to createContext - the default? If you consume context outside a provider, you get that default value.

@jacobmparis Haha 😜

can react compiler tell if a context consumer is used outside of its provider?

@zirkelc_ @juemrami @rauchg I kinda like that 𝚢𝚘𝚞 𝚌𝚊𝚗 𝚓𝚞𝚜𝚝 𝚍𝚘 𝚒𝚝 𝚏𝚛𝚘𝚖 𝚢𝚘𝚞𝚛 𝚋𝚛𝚘𝚠𝚜𝚎𝚛 dev tools too

@juemrami @rauchg Nope, this is me not knowing about it and sharing something (maybe) useful

I always wondered how @rauchg formats code snippets as monospace in tweets Searched the web, asked Grok & Co, but got zero results So I copied the actual snippet and asked Claude Turns out they're Unicode Mathematical Monospace chars, the styling is baked into the codepoints

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.

@vvaltterisa Could you open a github discussion with error/issue you are having? github.com/vercel/next.js…

so nextjs docs for eslint are completely broken?

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

@favourukonu_ What do you have in your package.json for the dev script?

@icyJoseph_dev It does start but still goes back to 3000 On my end, running without the double — throws an error 🥲

Trying to run two Next.js apps locally but they’re both sticking to the same port. -p 3001 isn’t working. What am I missing😭?