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 DEVTOOLS FACADE LANDS WITH PROFILER AND COMPONENT TREE TOOLS

By RepoJournal · Filed · About Meta

React's new DevTools Facade can now coexist with the browser extension, unblocking the entire integration strategy for embedded React inspection.

The React team shipped the final pieces of DevTools Facade this cycle, starting with the critical fix that lets `installFacade` attach to pages that already have a DevTools backend [1]. Without this, users with the React DevTools browser extension installed would lose access to it when Facade tried to install, a non-starter for adoption. The foundation landed first [2] with `createTools(facade)` that reads tracked state and returns plain JavaScript values, leaving serialization to the caller. On top of that, the profiler tools shipped [3] with `startProfiling()`, `stopProfiling()`, and `getTraceOverview()` for per-commit render timing. The team backed all this up with comprehensive test coverage [4] validating multi-root and multi-renderer scenarios. Meanwhile, React also fixed a Fizz streaming bug [5] where postponed state snapshots become stale after the prelude flushes, catching the `nextSegmentId` count at the right moment.

Action items

References

  1. [1] [react-devtools-facade] 5/ support an already-installed DevTools hook ↗ facebook/react
  2. [2] [react-devtools-facade] 2/ implement component tree tools ↗ facebook/react
  3. [3] [react-devtools-facade] 3/ implement profiler tools ↗ facebook/react
  4. [4] [react-devtools-facade] 4/ multi-root and multi-renderer tests ↗ facebook/react
  5. [5] [Fizz] Finalize postponed nextSegmentId after the prelude flush ↗ facebook/react
  6. [6] Migrate StyleSheet pure-logic Jest tests to Fantom (#57260) facebook/react-native
  7. [7] Migrate Blob, Network, and WebSocket Jest tests to Fantom (#57266) facebook/react-native
  8. [8] Migrate Image, Text, and NativeComponent Jest tests to Fantom (#57262) facebook/react-native
  9. [9] Delete interface.js (Flow), relocate __DEV__ global (#57275) facebook/react-native
  10. [10] Standardize secondary package READMEs (#57273) facebook/react-native

FAQ

What changed in Meta on June 19, 2026?
React's new DevTools Facade can now coexist with the browser extension, unblocking the entire integration strategy for embedded React inspection.
What should Meta teams do about it?
Review DevTools Facade integration if you're building embedded React inspection • Update your React Native test suites to track Fantom migration for Jest-to-Hermes parity • Verify Fizz streaming behavior if you rely on postponed state in Server Components
Which Meta repositories shipped on June 19, 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.