Quick Facts
- Category: Technology
- Published: 2026-05-12 04:37:27
- Alphabet’s AI Drug Unit Isomorphic Labs in Talks for $2B+ Funding Round
- Critical 'Bleeding Llama' Flaw Exposes Ollama Servers to Memory Theft
- Breaking: Everyday Movements Trigger Brain's Hidden Cleanup System
- Keto Diet Shows Promise as Treatment for Severe Mental Illness in Landmark Studies
- Revolutionizing Development: OpenAI’s GPT-5.5 and NVIDIA’s Codex Transform Enterprise Workflows
A Milestone Release
We are thrilled to announce the release of React Native 0.82, a landmark version that marks the first time React Native runs entirely on the New Architecture. This release signals the start of a new era for the framework, as we prepare to phase out the remaining legacy code in future versions to reduce package size and streamline the codebase.
Alongside this architectural shift, React Native 0.82 introduces an experimental opt-in for Hermes V1, the next major version of our JavaScript engine. It also ships with React 19.1.1, unlocking several new React features, and includes support for DOM Node APIs.
Key Highlights of React Native 0.82
- New Architecture Only – No legacy architecture fallback.
- Experimental Hermes V1 – Opt-in to the latest Hermes version.
- React 19.1.1 – Updated React core with new capabilities.
- DOM Node APIs – Enhanced web compatibility.
New Architecture Only: The Single Path Forward
Since React Native 0.76 made the New Architecture the default, we have rigorously tested and refined it. Now, with 0.82, the New Architecture becomes the only supported architecture. Any attempts to set newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS will be ignored—your application will always run on the New Architecture.
How to Migrate to React Native 0.82
If you haven’t migrated yet, follow these steps:
- Upgrade to React Native 0.81 or Expo SDK 54 – These are the last versions that allow legacy architecture. They include warnings and performance improvements to ease migration.
- Enable the New Architecture on 0.81 and thoroughly test your application to ensure everything works.
- Update to React Native 0.82 once you are confident with the New Architecture in 0.81. Version 0.82 prevents re-enabling the legacy architecture.
If a third‑party dependency blocks your migration, contact the library maintainers directly. For bugs in React Native core, please submit an issue on our issue tracker.
Interop Layers and Third‑Party Library Compatibility
We are keeping the interop layers in the codebase for now to ease the transition. All classes and functions required by these layers will remain available. Further announcements about their eventual removal will come in the future.
We have verified that third‑party libraries offering backward compatibility with both architectures continue to work seamlessly with React Native 0.82, even though only the New Architecture is present.
Removal of Legacy Architecture Classes
To minimize breaking changes, we are not removing any legacy APIs from the core in this version. However, eliminating legacy code will significantly reduce bundle size, so removal is scheduled to begin with the next React Native release. For more details, see RFC0929: Removal of the Legacy Architecture of React Native.
Experimental Hermes V1
React Native 0.82 offers an experimental opt‑in to Hermes V1, the next generation of our JavaScript engine. This version brings performance improvements and new capabilities. You can enable it in your app’s configuration. Note that it is still experimental; we welcome feedback and bug reports.
React 19.1.1 and DOM Node APIs
The update to React 19.1.1 unlocks several new features, including improved concurrent rendering and better developer tooling. Additionally, support for DOM Node APIs brings React Native closer to the web platform, enabling more consistent code between web and mobile applications.
Looking Ahead
React Native 0.82 is a pivotal release that simplifies the architecture and sets the stage for a leaner, faster framework. We encourage all developers to begin migration planning now. With the New Architecture as the sole path forward, the ecosystem can converge on a single, modern foundation.
Stay tuned for the next version, where we will begin removing legacy code to further reduce app size and improve performance.