The Wire · Showcase
REACT FLIGHT OPTIMIZES JSON SERIALIZATION, NATIVE CLEANS UP FEATURE FLAGS
By RepoJournal · Filed · About Meta
React's server-side Flight layer is now faster by moving model resolution outside the JSON.stringify path, while React Native is shipping four separate feature flag removals that consolidate months of internal experimentation.
The React team landed a critical optimization in Flight's serialization layer [1], pulling toJSON handling into an explicit recursive resolution step that lets V8 use its faster single-argument JSON.stringify call instead of the replacer function path. This follows performance advice from earlier PRs and unblocks downstream work on server component serialization. Meanwhile, the Rust compiler work on WTF-16 string handling [2] is shipping as the final piece of a boundary trilogy, fixing a long-standing issue where lone surrogates couldn't round-trip through the compiler without marker encoding hacks. React Native is consolidating its feature flag infrastructure by removing four separate gates: the optimized view registry path is now always-on on Android [4], hiding offscreen virtual views no longer toggles on iOS [5], the differentiator mutation pre-allocation defaults to off [6], and useNativeDriver can now be force-enabled via featureflag [3]. These aren't regressions; they're codifying what internal testing proved stable, cutting maintenance surface area across the codebase.
Action items
- → Review Flight serialization impact on your server components if you ship React 19+ facebook/react [plan]
- → Test React Native upgrade path for Android and iOS rendering if you use Animated APIs facebook/react-native [monitor]
- → Audit any custom feature flag extensions that depended on removed gates facebook/react-native [plan]
References
- [1] [Flight] Resolve models before JSON.stringify (#36795) facebook/react
- [2] [rust-compiler] Represent string values as JsString (WTF-16 aware) ↗ facebook/react
- [3] remove `useNativeDriver` under featureflag animatedForceNativeDriver (#57211) facebook/react-native
- [4] Remove useOptimizedViewRegistryOnAndroid feature flag (#57228) facebook/react-native
- [5] Remove hideOffscreenVirtualViewsOnIOS feature flag (#57225) facebook/react-native
- [6] Remove enableDifferentiatorMutationVectorPreallocation feature flag (#57224) facebook/react-native
FAQ
- What changed in Meta on June 17, 2026?
- React's server-side Flight layer is now faster by moving model resolution outside the JSON.stringify path, while React Native is shipping four separate feature flag removals that consolidate months of internal experimentation.
- What should Meta teams do about it?
- Review Flight serialization impact on your server components if you ship React 19+ • Test React Native upgrade path for Android and iOS rendering if you use Animated APIs • Audit any custom feature flag extensions that depended on removed gates
- Which Meta repositories shipped on June 17, 2026?
- facebook/react, facebook/react-native