Introduction
React Native 0.82 marks a pivotal moment in the framework's evolution. This release is the first to operate entirely on the New Architecture, leaving behind the legacy system that powered earlier versions. The React Native team views this as the dawn of a new era, with plans to phase out all remaining legacy code in upcoming updates to reduce bundle size and streamline the codebase.
Alongside this core change, version 0.82 introduces an experimental opt-in for Hermes V1, updates React to version 19.1.1, and adds support for DOM Node APIs. These enhancements are designed to improve performance, developer experience, and compatibility with modern web standards.
New Architecture Only
Since React Native 0.76 made the New Architecture the default, the team has continued to refine and test it extensively. With 0.82, the New Architecture becomes the only architecture. Any attempts to revert to the legacy system—such as setting newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS—will be ignored. Your application will run exclusively on the New Architecture regardless of these configurations.
How to Migrate to React Native 0.82
If you haven't yet moved your project to the New Architecture, follow these steps to ensure a smooth transition:
- Upgrade to React Native 0.81 or Expo SDK 54—these are the final versions that still support the Legacy Architecture. They include specific warnings and performance improvements to help you prepare for the change.
- Enable the New Architecture while still on 0.81, and thoroughly verify that your application functions correctly.
- Update to React Native 0.82 once you confirm everything works. This version blocks the Legacy Architecture entirely.
If a third-party dependency is incompatible and preventing migration, contact the library maintainers directly. For bugs in React Native core that block your migration, report them through the official issue tracker.
Interop Layers and Third-Party Library Compatibility
The interop layers that bridge the New and Legacy Architectures will remain in the codebase for the foreseeable future. All classes and functions required by these layers will not be removed soon. The team will share updates about their eventual removal later.
Third-party libraries that currently provide backward compatibility with both architectures will continue to work in 0.82, even though only the New Architecture is available.
Removal of Legacy Architecture Classes
To minimize breaking changes, React Native 0.82 does not remove any Legacy Architecture APIs from the core. However, the team plans to begin removing the legacy system starting with the next major version. This removal will significantly reduce the overall bundle size. For more details, see RFC0929: Removal of the Legacy Architecture.
Experimental Hermes V1 and React 19.1.1
Version 0.82 ships with an experimental opt-in to Hermes V1, a newer version of the JavaScript engine that promises improved startup times and lower memory usage. Additionally, React has been updated to version 19.1.1, which brings the latest React features and bug fixes. The inclusion of DOM Node APIs further bridges the gap between React Native and standard web development, allowing developers to work with familiar DOM-like interfaces.
What This Means for the Future
React Native 0.82 is more than an incremental update; it's a deliberate step toward a leaner, more modern framework. By committing solely to the New Architecture, the team can focus on optimization and innovation without the burden of maintaining two separate systems. Developers should prepare for the eventual removal of the Legacy Architecture in the next release, which will unlock further size reductions and performance gains.
For those already on the New Architecture, the transition to 0.82 should be straightforward. For others, the migration path outlined above provides a clear roadmap. The React Native ecosystem is evolving, and this release marks a key milestone in that journey.