React Native 0.82: A Major Leap Forward

React Native 0.82 marks a significant turning point for the framework, as it becomes the first version to run entirely on the New Architecture. This release also introduces several experimental features and updates, including support for Hermes V1, React 19.1.1, and DOM Node APIs. Below, we answer key questions about what this means for developers and how to prepare for the changes.

What is the most important change in React Native 0.82?

The biggest change is that React Native 0.82 runs exclusively on the New Architecture. This means the Legacy Architecture is no longer supported. If you try to disable the New Architecture using newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS, those settings will be ignored. React Native 0.82 ensures that all apps use the New Architecture, which has been tested and refined since becoming the default in version 0.76. This shift lays the groundwork for future performance improvements and a smaller bundle size.

Why is the New Architecture now the only option?

Since React Native 0.76, the New Architecture has been the default, and the team has spent time testing and stabilizing it. With version 0.82, they are confident enough to make it the sole architecture. This decision streamlines development, reduces maintenance burden, and eliminates the need to support two parallel codebases. In future versions, remaining Legacy Architecture code will be removed to further shrink install size and simplify the codebase. For now, backward-compatible APIs remain in place to ease the transition for existing projects.

How should developers migrate their projects to React Native 0.82?

If you haven’t migrated yet, here’s the recommended path:

• First, update your project to React Native 0.81 or Expo SDK 54 — the last versions that still allow using the Legacy Architecture. These releases include warnings and performance enhancements to help you switch.
• Enable the New Architecture in 0.81 and test thoroughly to confirm your app works correctly.
• Once you are successfully running on the New Architecture in 0.81, upgrade to React Native 0.82, which blocks the Legacy Architecture.

If a third‑party dependency prevents migration, contact the library maintainers. If you encounter a core bug, report it via the React Native issue tracker.

Will third‑party libraries still work in React Native 0.82?

Yes. The React Native team has kept the interop layers in place for the foreseeable future, ensuring that libraries that offer backward compatibility with both architectures will continue to function. All classes and functions needed by these interop layers will not be removed anytime soon. However, the team plans to share further updates about the eventual removal of interop layers. For now, developers can rely on most third‑party libraries that already support the New Architecture.

What is Hermes V1 and why is it experimental in this release?

Hermes V1 is an updated version of React Native’s JavaScript engine, designed for improved performance and smaller binary size. In React Native 0.82, it is available as an experimental opt‑in. This means developers can choose to enable it but should be aware that it may not be fully stable. The team encourages testing Hermes V1 in non‑production environments to help identify issues. If it proves reliable, it could become the default in a future release.

What are the key highlights of React Native 0.82?

The release comes with four main highlights:

1. New Architecture Only – Legacy Architecture is no longer supported.
2. Experimental Hermes V1 – An updated JavaScript engine available as an opt‑in.
3. React 19.1.1 – The latest version of React, bringing new features and optimizations.
4. DOM Node APIs – Support for additional DOM‑like APIs, making web‑to‑mobile transitions smoother.

These changes aim to improve developer experience and app performance while preparing the framework for future enhancements.

Will Legacy Architecture classes be removed immediately?

No. In React Native 0.82, the team is not removing any Legacy Architecture APIs from the core framework. This is done to ensure backward compatibility and reduce breaking changes. However, the removal process is scheduled to begin with the next version. This will significantly reduce bundle size and simplify the codebase. Developers are encouraged to start planning for that transition now. More details can be found in RFC0929: Removal of the Legacy Architecture of React Native.