Been using this repo to iterate on API ideas for a concurrent compatible store for React. Still exploratory but excited that we’re very close to something that we can start trying out with existing data stores and start an iteration cycle based on what we learn.

As an experiment, we (the Firefox team) wanted to try a new way to get feedback on which Interop proposals matter most.

So, here's a web app where you can rank the proposals you care about, giving us data we can use when reviewing which ones to champion.

interop-rank.jakearchibald.com

React 19.2 is now available!

This release includes Activity, useEffectEvent, React Performance Tracks, partial pre-rendering, and more:

react.dev/blog/2025/10...

i wrote about atproto and why it matters

done

⚛️📝 New on Overreacted: What Does "use client" Do?

Today we're sharing that View Transitions and Activity are ready to try in the experimental channel, along with docs and updates on other areas we're actively working on:

react.dev/blog/2025/04...

Today brings 84 new features in Safari 18.4!
• Declarative Web Push
• Screen Wake Lock API for Home Screen Web Apps
• Viewport presets in Responsive Design Mode
• Ogg Opus & Vorbis
• Image Capture API
• WebM support in MediaRecorder
• `view-transition-name: match-element`

webkit.org/blog/16574/w...

🎉 Exciting news! The Unicode MessageFormat 2.0 (MF2) specification is here! 🚀 This marks a huge milestone in our multi-year effort around improving how we localize software and eventually, the web. Check out the announcement:

🔗 blog.unicode.org/2025/03/unic...

You can pass sub-classed Promises to React such as in use() with the fields status and value or reason.

This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync().

Microtasks are bad, mkay.

Web development is easy. All you need to do is build a fully asynchronous, distributed system, serving an unknown set of clients over an unreliable network

react@19.0.0-rc1 is out today with a replacement for sibling pre-rendering. Give it a try and maybe we can ship React 19 soon?

github.com/facebook/rea...

This fix for this is so slick: instead of reverting back to the old behavior where Suspense fallbacks have to wait for suspended siblings to render, the new feature commits fallbacks immediately, then schedules a render for the siblings after to "pre-warm" the lazy requests in the tree.

🎉 After six incredible years at Framer, it’s time for my next step.

Today, we’re spinning Framer Motion out as its own independent open-source project, to better serve the whole community.

Introducing Motion. For React, and now, for everyone.