Who contributed to Meta on July 22, 2026?

6 developers shipped this update, including Josh Story, eps1lon, Hanno J. Gödecke, Carlos Enumo, Alex Hunt, and Christian Falch.

What were the notable Meta updates?

19.0.8 (July 21st, 2026), 19.1.9 (July 21st, 2026), and [FlightReply] Performance improvements when decoding.

Jul 22, 2026

$ the-wire · showcase

React 19 Cuts Server Component Decoding Time, React Native Fixes requestIdleCallback Regression

By RepoJournal · Filed 06:59 UTC on July 22, 2026 · About Meta · Composed from the cited sources · methodology

6 people shipped this

eps1lon @eps1lon 3 cited

Alex Hunt @huntie 2 cited

Josh Story @gnoff 1 cited

Carlos Enumo @pakerwreah 1 cited

Christian Falch @chrfalch 1 cited

Hanno J. Gödecke @hannojg

React shipped performance wins across 19.0.8 and 19.1.9 while React Native patched a critical timeout bug that broke requestIdleCallback tasks.

In brief

React 19 speeds up Server Component decoding. FlightReply payloads parse faster now. it's the kind of invisible win that matters when you're streaming 50KB of serialized data per request.
React Native 0.76 fixes requestIdleCallback timeout regression. the timeout was never getting assigned to native callbacks. one line fix, but it broke priority scheduling for half the ecosystem.
React 19.1.9 lands the same week as 19.0.8. both minor bumps. migration path's staying smooth, but the release cadence is tightening.
React 19 now handles blur events on Fragments nested below Document. edge case fix, but Fragment blur handling's been janky for years.

React's Server Components got faster overnight. Both 19.0.8 and 19.1.9 landed performance improvements when decoding [1][2], addressing a key bottleneck in the hot path for streaming payloads. The fix came alongside a security patch release [3], so audit your dependencies for the full changelog.

On React Native, the bigger story is a regression fix that shipped silently. The requestIdleCallback timeout was never assigned after a refactor [4], meaning tasks would hang indefinitely instead of respecting deadline constraints. This landed in production for teams running the latest native stack, so if your scheduled work feels stuck, this is your culprit.

Three cleanup PRs landed across the board [6][7][8]. React Native is migrating Node.js builtin imports to the node: scheme, dropping stale Flow suppressions, and fixing iOS version stamping in the prebuild pipeline. These are mostly internal hygiene, but the node: migration signals the direction of travel for Node compatibility going forward.

One more fix worth catching: React's Fragment blur handler was crashing when ownerDocument returned null instead of a Document [5]. Small edge case, but it'll save you a null reference error if you're handling focus on fragments near document boundaries.

Action items

→ Upgrade React to 19.0.8 or 19.1.9 for Server Component performance and security patches facebook/react [plan]
→ Patch React Native requestIdleCallback regression immediately if you use scheduled tasks facebook/react-native [immediate]
→ Test Fragment blur handling after upgrading React, especially near document boundaries facebook/react [monitor]

References

[1] 19.0.8 (July 21st, 2026) ↗ facebook/react
[2] 19.1.9 (July 21st, 2026) ↗ facebook/react
[3] [FlightReply] Performance improvements when decoding ↗ facebook/react
[4] fix(requestIdleCallback): timeout not assigned at NativeIdleCallbacks (#57571) ↗ facebook/react-native
[5] [DOM] Handle blur on Fragments below `Document` ↗ facebook/react
[6] Drop stale $FlowFixMe suppressions for node: imports (#57612) ↗ facebook/react-native
[7] Migrate Node.js builtin imports to node: scheme (#57611) ↗ facebook/react-native
[8] fix(iOS): stamp the React Native version in the prebuild compose job (#57603) ↗ facebook/react-native