React Native 0.82: Exclusive New Architecture & More

Welcome to a pivotal moment in React Native's evolution. Version 0.82 marks the first release that runs entirely on the New Architecture, leaving behind the legacy system for good. This update also brings an experimental Hermes V1, React 19.1.1, and support for DOM Node APIs. Whether you're a long-time developer or just getting started, this guide answers your key questions about what's new, how to migrate, and what this means for your projects.

What makes React Native 0.82 a milestone release?

React Native 0.82 is the very first version that operates exclusively on the New Architecture. In earlier releases, the New Architecture was the default but still allowed fallback to the Legacy Architecture. Starting with 0.82, that safety net is gone – the Legacy Architecture is no longer available. This decision comes after extensive testing and refinement of the New Architecture, which has proven to be more performant and stable. The team plans to remove remaining Legacy code in future versions to shrink bundle size and streamline the codebase. Alongside this architectural shift, 0.82 introduces an experimental opt-in for Hermes V1, updates React to version 19.1.1, and natively supports DOM Node APIs. These changes collectively aim to modernize React Native, making it faster, smaller, and more aligned with web standards.

React Native 0.82: Exclusive New Architecture & More

How does the exclusive New Architecture affect existing projects?

If your app is already running on the New Architecture, upgrading to 0.82 should be straightforward. However, any project that still relies on the Legacy Architecture will be affected. Setting newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS is now ignored; the New Architecture will always be used. This means you must migrate before upgrading. For those still on the Legacy Architecture, the recommended path is to first upgrade to React Native 0.81 or Expo SDK 54 – the last versions that support the Legacy Architecture. Enable the New Architecture there, verify everything works, and then move to 0.82. The migration guide provides step-by-step instructions. Also note that interop layers for third-party libraries remain supported for now, so most compatible libraries will continue to work as long as they are New Architecture-ready.

What is Hermes V1 and how do I opt in?

Hermes V1 is an experimental upgrade to the Hermes JavaScript engine used by React Native. It promises better performance, smaller bundle sizes, and improved memory usage. In 0.82, Hermes V1 is not enabled by default – you must opt in explicitly. To do so, configure your build settings to use a specific Hermes version. On Android, you can set hermesVersion in your android/app/build.gradle file. On iOS, adjust your Podfile or use a pre-release CocoaPods spec. Keep in mind that this is still experimental, so you may encounter edge cases. The team encourages developers to test it thoroughly in staging environments before rolling out to production. For more details, check the feature highlights section or the official React Native documentation on Hermes configuration.

What new features come with React 19.1.1 and DOM Node APIs?

React Native 0.82 ships with React 19.1.1, bringing the latest React features like improved concurrent rendering patterns, automatic batching, and new hooks. Additionally, DOM Node APIs are now natively supported, allowing direct manipulation of mounted nodes – similar to the getElementById or querySelector you might use on the web. This is a major step toward unifying React web and React Native development. For example, you can now call findNodeHandle(componentRef).getBoundingClientRect() or attach event listeners directly to native views. These APIs are experimental and may evolve, but they open up powerful possibilities for complex interactions and custom navigation solutions. Combined with the performance gains from the New Architecture and Hermes V1, 0.82 sets a new standard for what React Native can achieve.

What is the recommended migration path to React Native 0.82?

Follow these steps to safely move to version 0.82:

Upgrade to React Native 0.81 or Expo SDK 54 – these are the last versions that allow the Legacy Architecture. They include warnings and tools to help you migrate.
Enable the New Architecture in that version by setting appropriate flags. Test your app thoroughly to ensure all features and third-party libraries work.
Verify compatibility – check that your custom native modules and community packages are updated for the New Architecture. If blocked by a third-party dependency, contact the library maintainers directly. For core bugs, report via the React Native issue tracker.
Upgrade to 0.82 once everything runs smoothly on the New Architecture. After this point, legacy architecture flags are ignored, and your app will use the New Architecture exclusively.

The interop layers that bridge old and new architectures will remain in place for the foreseeable future, so most libraries that supported both architectures should continue working. Stay tuned for future updates as the team plans to remove these layers later.

Will third-party libraries need to update for React Native 0.82?

Third-party libraries that already support the New Architecture – meaning they offer backward compatibility with both old and new architectures – will keep working in 0.82. The React Native team has verified that the interop layers, which allow Legacy Architecture components to function in the New Architecture environment, remain active for now. However, any library that only works with the Legacy Architecture must be updated. If you're depending on such a library, you should reach out to the maintainers and request a New Architecture-compatible version. In the long term, the interop layers will be removed (planned for a future release), so it's wise to begin migrating your dependencies as soon as possible. For a smooth experience, verify that your entire tech stack is New Architecture-ready before upgrading to 0.82.

Tags: