RepoJournal
Meta

Meta

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

Pick a date

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

The Wire · Showcase

REACT NATIVE KILLS LEGACY ARCH, BUMPS NODE 22

By RepoJournal · Filed · About Meta

React Native is ripping out the feature flags that held back Fabric adoption and raising the Node.js floor by two major versions in the same commit wave.

The mobile team is finishing what it started: removing the `enableFabricRenderer()` flag entirely [1] [2], which always returned true on canary anyway. This is cleanup that signals Fabric is no longer experimental. They're also guarding legacy architecture tests behind compile macros [3] to stop build failures when old code paths get stripped. On tooling, React Native now requires Node.js 22.13.0 or better [4], dropping Node 20 entirely after it hit end-of-life in April 2026. This aligns with Metro's upcoming requirements and forces the ecosystem forward. A minor iOS fix removes unnecessary window handling code in LogBox on Mac Catalyst [5]. Over in Jest, Babel got bumped to rc.5 [6], and the team shipped mandatory changelog enforcement [7] [8] to keep PR history clean. They also nuked the unmaintained jest-pnp-resolver [10], replacing it with unrs-resolver 1.12.1 [9].

Action items

References

  1. [1] Delete enableFabricRenderer() from ReactNativeNewArchitectureFeatureFlags (#56860) facebook/react-native
  2. [2] Inline true in ReactDelegate.isFabricEnabled initializer (#56859) facebook/react-native
  3. [3] Guard cxxreact MethodCall tests under legacy-arch macro (#56902) facebook/react-native
  4. [4] Bump minimum Node.js version to 22 (#56887) facebook/react-native
  5. [5] Remove makeKeyWindow call in RCTLogBoxView dealloc (#56861) facebook/react-native
  6. [6] chore(deps): update babel monorepo to v8.0.0-rc.5 ↗ facebook/jest
  7. [7] chore: enforce changelog entry on PRs via GitHub Actions ↗ facebook/jest
  8. [8] chore: enforce more rules on changelog entries ↗ facebook/jest
  9. [9] chore: bump `unrs-resolver` to 1.12.1, remove `jest-pnp-resolver` and unnecessary checks ↗ facebook/jest
  10. [10] chore: bump `unrs-resolver` to 1.12.1, remove `jest-pnp-resolver` and unnecessary checks (#15721) facebook/jest

FAQ

What changed in Meta on May 20, 2026?
React Native is ripping out the feature flags that held back Fabric adoption and raising the Node.js floor by two major versions in the same commit wave.
What should Meta teams do about it?
Update to Node.js 22.13.0+ immediately if you maintain React Native tooling • Plan migration off Node 20 for any projects building React Native apps • Monitor Babel 8.0 rc releases if using Jest with custom Babel configs
Which Meta repositories shipped on May 20, 2026?
facebook/react-native, facebook/jest

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.