@zachtratar@ivanhzhao Congrats on the launch. I have some feedback from my colleagues and me regarding Notion AI. What is the best way to share them with you and the team?
Vercel will be officially sponsoring https://t.co/QF7eOed81b. That's a given. We as a community and industry owe @adamwathan and team a lot. Tailwind is foundational web infrastructure at this point (it fixed CSS ๐). I've also reached out to Adam to explore how we can make this a longer-term commitment.
2025 React Aria year in review ๐
๐ New components: Autocomplete, Disclosure, Toast, Tree, Virtualizer
๐ Major features: Multi-Select, Tree drag and drop, built-in animations, infinite scrolling, ComboBox actions, unit testing library.
๐ Important updates: Improved interoperability โ rewrote usePress, opened DOM events, support custom trigger elements, etc.
๐ฅณ Last but definitely not least: completely re-built docs!
Looking forward to 2026!
You can now install all React Aria components in a single command! Choose Tailwind or vanilla CSS, install, and customize. ๐
npx shadcn add @โreact-aria/tailwind
npx shadcn add @โreact-aria/css
๐ [email protected] is out, where @kdy1dev rewrote the AST transformer for useExtracted in Rust!
๐ ~45% faster processing time
โ Support for source maps
https://t.co/UvpJCEsi7l
๐ Self-hosting Next.js has just received a massive upgrade!
@platformatic Watt v3.18 brings Vercel-level distributed caching to YOUR infrastructure with Next.js 16's 'use cache' directive + Redis/Valkey.
No more cache inconsistencies. No more wasted resources. Production-ready scale.
Here's how ๐งต
@huozhi could you have more debugging features?
(PoC) for debugging which function causes dynamic rendering - this is a PITA issue
https://t.co/bL21OTzTPI
@timneutkens Could we show debug log why a route is using dynamic rendering and to display the stack trace of the root cause?
IIUC, we already have a similar feature when exporting static pages. The current developer tool indicates whether the page is static or dynamic,but not the root cause
@timneutkens Could we show debug log why a route is using dynamic rendering and to display the stack trace of the root cause?
IIUC, we already have a similar feature when exporting static pages. The current developer tool indicates whether the page is static or dynamic,but not the root cause
Regarding Guillermo-Gate, I've seen people use it as a reason to boycott OSS projects.
Going after OSS projects that are openly governed isn't going to do what you want it to. Vercel makes its money from its hosting platform and paid products. OSS is not a paid product and while contributes goodwill doesn't directly impact the bottomline. And these project's reach well exceed Vercel.
First the list is longer than you think. Yes Next, Svelte/SvelteKit, Webpack, SWC, TurboRepo. There are also Nuxt, Nitro, React. Seb, the current visionary of the React team, as well as Andrew work at Vercel, not Meta. Should we boycott React metaframeworks too? Remix/RR, Tanstack React? Good luck finding projects that haven't received money from Vercel in the past.
Secondly impact. When you realize things Nitro/UnJS that exist to keep the platform open and not locked in to a single deployment platform, and are used outside of Vercel (Tanstack Start, SolidStart, Analog). Or Webpack/SWR which power countless projects it is difficult to make this about Vercel.
Third, I've seen the suggestion that Vercel acquires OSS the way one does companies. It doesn't work like that. The way you kill off OSS is easy. Remove their source of funding. NuxtLabs could have gone under and took Nuxt with it. I've seen this happen to other projects.
More so because these are open projects, it isn't like you buy their customers. You can still deploy Nuxt/SvelteKit anywhere. It creates good will, but they can go anywhere. There are no contracts. NuxtLabs was a company, but Nuxt isn't. These are more like charity foundations.
Next.js and Turbopack now support the TC39 Debug ID proposal.
This was the last blocker for native https://t.co/7vUgT50kRz support when using `next build --turbopack`.
Sentry Next.js SDK update coming soon.
Great work by @lukeisandberg on adding the feature and thanks to @LucaForstner and Charly from Sentry for collaborating on this.