What should Meta teams do about it?

Upgrade React to include devtools-facade hook inspection fix [ref:1] if you're debugging complex hook interactions • Review React 19.x patch notes now that they're in the changelog [ref:2] to catch any silent fixes you missed • Pull React Native's backwards compat and prop validation fixes [ref:8], [ref:10] before your next bridge upgrade

Which Meta repositories shipped on June 30, 2026?

facebook/react, facebook/react-native

REACT DEVTOOLS GAINS HOOK INSPECTION CONTROL, REACT NATIVE PATCHES BACKWARDS COMPATIBILITY GAPS

By RepoJournal · Filed 06:03 UTC on June 30, 2026 · About Meta

React's developer tooling now lets you toggle hook tree inclusion in component inspection, while React Native is quietly fixing the cascading prop validation failures exposed by its new iterator-setter audit.

The devtools-facade update [1] adds a boolean flag to component lookup that controls whether hook inspection data appears in the payload, returning error details if hook requests fail. This matters because devtools has been opaque about what gets included when you inspect a component. Meanwhile, React's changelog landed missing patch notes [2] for the entire 19.x line (`.2` through `.8` across three version tracks), which should unblock anyone trying to figure out what actually shipped. On the streaming APIs front [3], React added test coverage exposing why the `string.length` fast path for multi-byte content is fundamentally broken: it undercounts UTF-8, causing the outlining heuristic to miss real boundaries that exceed 500 bytes. React Native is playing catch-up on its own breaking changes. The team discovered that `ReactDOM.preloadModule()` accepted a `nonce` option in its type definition but silently dropped it at runtime [4], and is now fixing the gap. More critically, React Native's new iterator-setter audit [7] surfaced six cases where prop keys parsed in constructors had no matching handler in `setProp` methods, creating silent failures as the codebase migrated to the new routing path. The team also restored a deprecated three-argument overload for `RawProps::at()` [5] to keep Nitro modules from breaking, and fixed a build artifact workflow that was failing because `VERSION_NATIVE_FB` only got written in one code path [6].

FAQ

What changed in Meta on June 30, 2026?: React's developer tooling now lets you toggle hook tree inclusion in component inspection, while React Native is quietly fixing the cascading prop validation failures exposed by its new iterator-setter audit.
What should Meta teams do about it?: Upgrade React to include devtools-facade hook inspection fix [ref:1] if you're debugging complex hook interactions • Review React 19.x patch notes now that they're in the changelog [ref:2] to catch any silent fixes you missed • Pull React Native's backwards compat and prop validation fixes [ref:8], [ref:10] before your next bridge upgrade
Which Meta repositories shipped on June 30, 2026?: facebook/react, facebook/react-native

REACT DEVTOOLS GAINS HOOK INSPECTION CONTROL, REACT NATIVE PATCHES BACKWARDS COMPATIBILITY GAPS

The showcase is a teaser. Your wire is the product.

The showcase is a teaser.
Your wire is the product.