RepoJournal
Meta

Meta

React, React Native, and Jest - the open source under what Meta ships

Keep up with Meta in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript AI / ML Full archive →

The Wire · Showcase

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

By RepoJournal · Filed · 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].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [react-devtools-facade] Add includeHooks option to component lookup ↗ facebook/react
  2. [2] [changelog] Add 19.0.x, 19.1.x, 19.2.x patch releases ↗ facebook/react
  3. [3] [test] Add coverage for multi-byte code units in stream APIs (#36900) facebook/react
  4. [4] [Float] Forward `nonce` option in ReactDOM.preloadModule() ↗ facebook/react
  5. [5] Add back backwards compat for rawProps.at(x,y,z) (#57346) facebook/react-native
  6. [6] Fix missing VERSION_NATIVE_FB in commit artifacts (#36889) facebook/react-native
  7. [7] Fix ctor/setProp prop-name gaps surfaced by iterator-setter audit (#57330) facebook/react-native

Quick answers

What shipped 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. In total, 19 commits and 4 pull requests landed.
Who contributed to Meta on June 30, 2026?
3 developers shipped this update, including hoxyq, eps1lon, and UditDewan.
What were the notable Meta updates?
[react-devtools-facade] Add includeHooks option to component lookup, [changelog] Add 19.0.x, 19.1.x, 19.2.x patch releases, and [test] Add coverage for multi-byte code units in stream APIs (#36900).

More from Meta

Daily updates, in your inbox

Follow Meta

Keep up with Meta in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.