React Native 0.84 Released — Hermes V1 Becomes the Default, Prebuilt iOS Binaries and Legacy‑Arch Removal

React Native 0.84 (stable) shipped on Feb 11, 2026. This is a platform release with practical, high‑impact changes for mobile and full‑stack teams: Hermes V1 is now the default JS engine, iOS builds use precompiled React Native binaries by default, the Legacy Architecture code has been removed from shipping builds, and the minimum Node.js requirement has been raised to Node 22.11+. Read the release notes before upgrading — this one affects build pipelines, native modules, and CI artifacts.

Why this matters (short)

• Hermes V1 default: All projects using the built‑in Hermes runtime will get the Hermes V1 VM/compiler automatically, improving cold starts, memory use, and runtime performance without code changes — but it can change engine semantics and native‑bridge timing characteristics.
• Precompiled iOS binaries by default: iOS clean builds are much faster because core RN code is downloaded as prebuilt .xcframeworks instead of compiled from source each build. This changes CI tooling and binary distribution strategies.
• Legacy Architecture removed: The code paths for the Legacy Architecture are now physically removed from shipped iOS/Android builds; projects relying on legacy internals or private APIs must rebuild from source or adapt.
• Node bump: Tooling and CI must run Node >= 22.11; older Node versions will break the React Native CLI and related scripts.

Immediate practical checklist for full‑stack teams

1. Add a canary branch and run your full CI matrix on react‑[email protected] before promoting to production:
   • Rebuild all native modules and publish/update prebuilt artifacts for the Node/V8/Hermes ABI you rely on.
2. CI / Developer environments:
   • Upgrade your CI images and local dev setup to Node 22.11+ (use nvm/fnm to pin versions).
   • If you use prebuilt iOS binaries in CI, validate the pod install step and artifact caching (RCT_USE_PREBUILT_RNCORE).
3. Native modules & prebuilt binaries:
   • Rebuild and test every native addon (C++/NDK, CocoaPods native code) against RN 0.84. Prebuilt iOS frameworks change how native code is linked — publish updated prebuilt binaries if you distribute them.
4. Opt‑out and compatibility paths:
   • To opt out of Hermes V1, build RN from source or pin the legacy hermes compiler via package manager overrides and follow platform-specific flags (examples are in the release notes).
   • To disable prebuilt iOS binaries, set RCT_USE_PREBUILT_RNCORE=0 during pod install.
   • To re-enable Legacy Architecture (if you must), you need to build from source and pass RCT_REMOVE_LEGACY_ARCH=0 and related flags.
5. Test for behavioral regressions:
   • Prioritize integration tests for bridging, timing‑sensitive code, animations, and any native APIs previously reached through legacy internals.
   • Check crash and telemetry pipelines for new error signatures from the updated V8/Hermes runtime and Node toolchain.
6. Tooling and linters:
   • Update ESLint config if you rely on RN's recommended tooling (RN 0.84 supports ESLint v9 flat config).
   • Verify any build‑time scripts or bundlers that assume older Node or legacy RN internals.
7. Accessibility and platform features:
   • Confirm the app’s accessibility behavior, especially on Android where recycled-view accessibility issues were fixed.
   • Validate image handling if you rely on HEIC/HEIF workflows.

Migration notes (practical)

• Staged rollout: land RN 0.84 in a staging track (internal beta) and roll progressively; monitor crashes and performance telemetry closely for the first 24–72 hours.
• Native prebuilds: if you ship prebuilt native binaries to customers or downstream teams, coordinate a simultaneous release of updated artifacts targeted at RN 0.84 to avoid installer/runtime mismatches.
• Backwards compatibility: projects already on Hermes and the New Architecture should see minimal functional changes, but verify third‑party native libraries that touch low‑level bridge APIs.

Bottom line React Native 0.84 is a meaningful platform bump — it gives most apps an immediate performance and developer‑experience win (Hermes V1 + faster iOS builds) but requires careful CI, native‑module, and Node tooling updates. Treat this as a platform upgrade: staged rollout, rebuild native artifacts, upgrade Node in CI, and run a focused test matrix that exercises native bridges and timing‑sensitive flows.

Source: React Native 0.84 release notes. (reactnative.dev)

Source

• Source