React Native 0.82: Everything You Need to Know About the New Architecture-Only Release

React Native 0.82 marks a major turning point for the framework. It’s the first version that runs entirely on the New Architecture, leaving the Legacy Architecture behind. This release also introduces an experimental Hermes V1, upgrades React to 19.1.1, and adds support for DOM Node APIs. If you're wondering how to migrate, what the changes mean for your apps, or what’s next for legacy code, this Q&A covers it all.

What Does “New Architecture Only” Mean in React Native 0.82?

Starting with version 0.82, React Native no longer supports the Legacy Architecture. Previously, developers could toggle between old and new architectures using flags like newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS. In 0.82, those flags are ignored — your app will always run on the New Architecture. This move builds on the foundation laid in 0.76, where the New Architecture became the default. After extensive testing and refinement, the team is confident enough to make it the only option. For future versions, legacy code will be gradually removed to reduce package size and simplify the codebase.

How Should I Migrate to React Native 0.82?

If you haven’t migrated yet, start by moving to React Native 0.81 or Expo SDK 54. These are the last versions that still allow you to use the Legacy Architecture. They include special warnings and performance improvements to ease your transition. After upgrading, enable the New Architecture in 0.81 and thoroughly test your application. Once everything works correctly, you can safely update to 0.82, which locks you into the New Architecture. If a third-party dependency is blocking your migration, reach out to its maintainer directly. For bugs in React Native core, report them via the official issue tracker.

Will Third-Party Libraries Still Work in React Native 0.82?

Yes, but with some important caveats. The React Native team plans to keep the interop layers in the codebase for the foreseeable future. These layers ensure that classes and functions needed for backward compatibility remain available. Third-party libraries that currently support both architectures should continue to function seamlessly in 0.82. However, the team will eventually remove these interop layers, so library maintainers should prepare for a future where only the New Architecture is supported. If you’re a developer, verify that your dependencies are updated to work with the New Architecture.

What Are the Key Highlights of React Native 0.82?

This release packs several major improvements. First, it ships with an experimental opt-in for Hermes V1, a newer version of the Hermes JavaScript engine that promises better performance and smaller bundle sizes. Second, React has been updated to version 19.1.1, enabling the latest React features. Third, support for DOM Node APIs is now included, bridging the gap between React Native and web development. Finally, the removal of the Legacy Architecture is a cornerstone change — though no APIs are removed in this version, the clean-up will begin in the next release, as outlined in RFC0929.

What Happens to Legacy Architecture Code in Future Versions?

In React Native 0.82, no Legacy Architecture APIs are removed. The team chose to keep them temporarily to reduce breaking changes and give developers more time to adapt. However, starting from the next version, legacy code will be systematically removed. This will significantly reduce the overall bundle size and streamline the codebase. The interop layers that currently bridge old and new code will also be phased out eventually. If you’re maintaining a library or an app that still relies on legacy APIs, now is the time to plan your migration to avoid disruptions.

How Can I Try the Experimental Hermes V1?

Hermes V1 is available as an optional, experimental feature in React Native 0.82. To enable it, you’ll need to configure your project to opt in. The exact steps depend on your setup, but generally you’ll modify the metro.config.js or add specific flags. Keep in mind that this version is experimental — it may not be as stable as the default Hermes, and some features might not work. It’s best to test it in a separate branch or staging environment. The team encourages feedback via the issue tracker to help improve Hermes V1 before it becomes the default in future releases.