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 FIZZ TIGHTENS ABORT SEMANTICS, FIXES WORK SCHEDULING VISIBILITY

By RepoJournal · Filed · About Meta

React's server-side rendering layer just became harder to misuse, with three commits that eliminate footguns in error handling and work scheduling that could silently swallow failures.

React Fizz is enforcing stricter abort semantics across three coordinated changes landing in the same window. First, abort reentrancy is now explicitly forbidden [1]. Previously you could contrive sequences where onError fired after a render already fataled, creating hard-to-debug timing issues. Now the request state machine rejects any abort attempt on a request that's already aborting, completed, or fataled. Second, when an abort does occur, all pending task errors now report correctly [2]. The old behavior let fatal errors suppress error reporting from tasks inside Suspense boundaries, making it impossible to surface what actually went wrong during an abort sequence. Third, Fizz's external work scheduling is now modeled explicitly in config [3], solving a reasoning problem: you could call scheduleWork with no guarantee it would execute in certain bundle configurations. These changes don't add features. They remove ways the system can lie to you about what happened.

Action items

References

  1. [1] [Fizz] Do not allow abort reentrancy ↗ facebook/react
  2. [2] [Fizz] Continue reporting aborted task errors after a fatal abort ↗ facebook/react
  3. [3] [Fizz] model fb bundle's external work scheduling explicitly ↗ facebook/react

FAQ

What changed in Meta on May 31, 2026?
React's server-side rendering layer just became harder to misuse, with three commits that eliminate footguns in error handling and work scheduling that could silently swallow failures.
What should Meta teams do about it?
Review your Fizz abort handling and error callbacks for timing-dependent logic • If you drive Fizz through external performWork calls, verify your scheduling config after upgrading
Which Meta repositories shipped on May 31, 2026?
facebook/react

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.