Yo

React Senior architect, Past experience in Angular, Sencha Extjs & JHipster

[shadcn @shadcn]

The @base_ui docs just went live 🚀

Components rebuilt. Examples refreshed. Docs rewritten. Look for the Base UI tab on component pages.

npx shadcn create → choose Radix or Base UI

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

📦 React Native macOS 0.81 + Windows 0.81

Both have New Architecture enabled by default 🥳

[Julian Garnier @JulianGarnier]

Introducing Auto Layout in Anime.js v4.3!

- Animate display flex / grid / none, etc.
- Enter / Leave animations
- Animate DOM position changes
- Interruptible animations
- Staggered children animations
- Supports any easing functions
- Dead simple API

Link below ⬇︎

[Josef Bender @josefbender_]

Why should you use @tan_stack Start?

→ Isomorphic Functions

You don't have to worry about WHERE a function is running.

Just define both implementation, and TanStack Start will call the correct one.

Here is a real-life example:

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

Dan Abramov just open-sourced a new RSC explorer tool 👀

It's an educational tool to understand how it all works

Both the client/server part of RSCs runs in your browser

[Szymon Rybczak @SzymonRybczak]

New React Native DevTools app is really awesome, finally standalone app! 😍

Network & Performance tracing panels are now available for every React Native app 💯

[React @reactjs]

There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it.

A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately.

https://t.co/kue7kd0XEX

[Next.js @nextjs]

A critical vulnerability in React Server Components (CVE-2025-55182) affects React 19 and frameworks, including Next.js (CVE-2025-66478).

All users should upgrade to the latest patched version in their release line.
https://t.co/azJJgxS67J

[The React Native Rewind @ReactNativeRwd]

𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗺𝗺𝗸𝘃 𝘃𝟰 is here — and as 𝗠𝗮𝗿𝗰 𝗥𝗼𝘂𝘀𝘀𝗮𝘃𝘆 teased at React Universe Conf 2025, it’s not just an update. It’s a 𝗿𝗲𝘄𝗿𝗶𝘁𝗲.

If you haven’t used it before — 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗺𝗺𝗸𝘃 𝗶𝘀 𝗮 𝗥𝗲𝗮𝗰𝘁 𝗡𝗮𝘁𝗶𝘃𝗲 𝗹𝗶𝗯𝗿𝗮𝗿𝘆 𝘁𝗵𝗮𝘁 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝘀 𝗳𝗮𝘀𝘁, 𝘀𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗼𝘂𝘀 𝗸𝗲𝘆-𝘃𝗮𝗹𝘂𝗲 𝘀𝘁𝗼𝗿𝗮𝗴𝗲 by wrapping Tencent’s MMKV engine — a native C++ library originally built for WeChat.

𝗨𝗻𝗱𝗲𝗿 𝘁𝗵𝗲 𝗵𝗼𝗼𝗱, Tencent’s MMKV stores data in memory-mapped files, giving near-instant read/write access directly from native memory.
By leveraging that engine through a native bridge, react-native-mmkv avoids the JSON serialisation and asynchronous bridge calls that make AsyncStorage slower.

This version marks the next major evolution of one of React Native’s most efficient storage solutions — 𝗿𝗲𝗯𝘂𝗶𝗹�� 𝗲𝗻𝘁𝗶𝗿𝗲𝗹𝘆 𝗼𝗻 𝗡𝗶𝘁𝗿𝗼 𝗠𝗼𝗱𝘂𝗹𝗲𝘀.

➡️ 𝗙𝘂𝗹𝗹 𝗡𝗶𝘁𝗿𝗼 𝗿𝗲𝘄𝗿𝗶𝘁𝗲 — meaning faster calls, cleaner bridging, and full compatibility with the New Architecture.
➡️ Works again on old architecture too (up until React Native 0.82).
➡️ Uses 𝗠𝗠𝗞𝗩𝗖𝗼𝗿𝗲 from CocoaPods/Gradle instead of bundling source — no more duplicate symbols when mixing with native code.
➡️ set(...) now throws a useful error if a value can’t be saved
➡️ remove(...) returns a boolean
➡️ useMMKVKeys() hook added
➡️ AppGroup support is back
➡️ remove() and clearAllKeys() now notify listeners properly

Under the hood, this version leans into the Nitro runtime, improving performance and reliability across both Android and iOS.

ℹ️ 𝗕𝗲𝗳𝗼𝗿𝗲 𝘂𝗽𝗴𝗿𝗮𝗱𝗶𝗻𝗴 — 𝗿𝗲𝗮𝗱 𝘁𝗵𝗲 𝗩𝟰 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗴��𝗶𝗱𝗲.
There are subtle but important breaking changes if you rely on older behaviours or manual native integrations.

What storage solution are you using in your React Native apps right now — MMKV, AsyncStorage, or something custom? 👇

#ReactNative #MMKV #NitroModules #Performance #MobileDev #OpenSource #ReactNativeRewind #NewArchitecture #AsyncStorage #MarcRoussavy

[Evan You @evanyou]

We don't talk enough about the effort that went into optimizing Oxc (which powers Rolldown, and by extension Vite 8 and beyond).

So we tracked down all the perf-improving PRs that went into Oxc - there are 479 of them!

[Rob Palmer @robpalmer2]

ECMAScript excitement 😉

Node.js 24 ships these new JS features 🎉

🔶 Atomics.pause
🔶 Error.isError
🔶 Explicit Resource Management (`using`)
🔶 Float16Array
🔶 Intl.DurationFormat
🔶 Promise.try
🔶 RegExp.escape
🔶 RegExp Modifiers
🔶 RegExp Duplicate Named Capture Groups

[Thomas Roccia 🤘 @fr0gger_]

New business card 😁

[RedwoodSDK @RedwoodJS]

The @vite_js team has opened an experimental PR in RedwoodSDK to use "react-server-dom-vite" instead of "react-server-dom-webpack"

We're excited that RSC is coming to Viteland! 🎉 It also means less code from our side!

https://t.co/E9GP8KmyhF

[Evan You @evanyou]

You might be getting tired of me sharing builds getting x times faster with Rolldown-Vite

But you’ll keep hearing more and more such cases in the next few months

[VoidZero @voidzerodev]

We are excited to announce that we are partnering with @nuxtlabs to have @antfu7 work on Vite Devtools!

https://t.co/rxXbk5FE1o

[React @reactjs]

React 19.1 has just been released! Check out the latest updates here: https://t.co/3SY0SABy48

[Evan You @evanyou]

I held this prediction very early on, but held off expressing it explicitly because I always respect how React team is willing to rethink best practices - some of those bets paid off handsomely - and I understand sometimes you gotta give new ideas the chance to iterate.

But deep down I never liked the direction, which is why I decided early on that we will not do something similar in Vue. Some of the benefits of RSC in static generation cases can be achieved without such a drastic paradigm shift. I have long had ideas on how to make them work in Vue/Vite and hope I can find some time to prototype it.

[Zack Jackson @ScriptedAlchemy]

ESM federation will work.
It also includes the fixes I made for React Router rsbuild plugin!

[Daishi Kato @dai_shi]

Some new Zustand users might not know this, so I'm posting it again. zustand/vanilla is just 23 loc.

[Daishi Kato @dai_shi]

🐻 Zustand hits 51k stars! ⭐️