RepoJournal
Meta

Meta

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

Pick a date

  1. Sat 16 may
  2. Sun 17 may
  3. Tue 19 may
  4. Wed 20 may
  5. Thu 21 may
  6. Sat 23 may
  7. Sun 24 may
  8. Tue 26 may
  9. Thu 28 may
  10. Fri 29 may
  11. Sat 30 may
  12. Sun 31 may
  13. Mon 1 jun
  14. Mon 8 jun
  15. Tue 9 jun
  16. Wed 10 jun
  17. Thu 11 jun
  18. Fri 12 jun
  19. Sat 13 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

REACT FIXES CONCURRENT ERROR RECOVERY BUG, DEVTOOLS GAINS COMPONENT LOOKUP

By RepoJournal · Filed · About Meta

React's error recovery logic was treating incomplete trees as complete, causing confusing downstream errors that could mask real failures.

The concurrent error recovery handler in React was checking for `RootErrored` status but overlooking `RootSuspendedAtTheShell`, which should also be treated as an errored state [1]. This means an incomplete tree that never entered the complete phase could be mistaken for a successful render, leading to silent failures and confusing error messages. Separately, React DevTools landed a major usability upgrade: you can now look up which component owns a DOM element in Chrome DevTools, starting with DOM element component lookup in the CDT MCP integration [2] and backed by a new `getComponentByHostInstance` tool in the Facade [3]. The full chrome-devtools-mcp integration is now live [4]. On the compiler front, React restored code frames in ESLint error messages after the Rust port stripped them out [5]. Over on React Native, the team is cleaning house: `Modal`'s deprecated `animated` prop is gone (use `animationType` instead) [7], and the redundant `animatedShouldUseSingleOp` feature flag has been removed [8]. A breaking change on Android: do not synchronize on java.lang.Boolean, preparing for JEP 401 value classes [6].

Action items

References

  1. [1] Fix: Treat incomplete tree as an error during recovery ↗ facebook/react
  2. [2] [react-devtools-cdt-mcp] add DOM element component lookup ↗ facebook/react
  3. [3] [react-devtools-facade] add host instance component lookup ↗ facebook/react
  4. [4] [react-devtools-cdt-mcp] chrome-devtools-mcp integration ↗ facebook/react
  5. [5] [compiler] Restore code frames in ESLint compiler error messages (#36901) facebook/react
  6. [6] Do not synchronize on java.lang.Boolean. (#56196) facebook/react-native
  7. [7] Remove Modal animated prop (#57385) facebook/react-native
  8. [8] Remove animatedShouldUseSingleOp feature flag (#57364) facebook/react-native

FAQ

What changed in Meta on July 1, 2026?
React's error recovery logic was treating incomplete trees as complete, causing confusing downstream errors that could mask real failures.
What should Meta teams do about it?
If using React concurrent features, upgrade immediately to get the error recovery fix • React Native users: remove any reliance on Modal's animated prop before next release • Monitor React DevTools for the new component lookup feature in your debugger workflow
Which Meta repositories shipped on July 1, 2026?
facebook/react, facebook/react-native

Related across the cluster

For your repos

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

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.