React Native 0.82 Drops Legacy Architecture Support – A New Era Begins

Breaking: React Native 0.82 Now Requires New Architecture

The React Native team has officially released version 0.82, marking the first release that exclusively runs on the New Architecture. Starting with this version, the old Legacy Architecture can no longer be used, even if developers attempt to set legacy flags.

This move signals the end of a transitional period that began with React Native 0.76, when the New Architecture became the default. In a statement, the team declared: “This is a milestone release and the start of a new era for React Native.”

What’s New in 0.82 Beyond Architecture

Alongside the mandatory New Architecture, React Native 0.82 introduces experimental support for Hermes V1, a new version of the Hermes JavaScript engine. Developers can opt into this upgrade to potentially boost performance.

The release also updates React to version 19.1.1, enabling several new React features. Additionally, support for DOM Node APIs has been added, allowing more direct manipulation of native views.

Highlights at a Glance

• New Architecture only (Legacy Architecture removed)
• Experimental opt-in to Hermes V1
• React 19.1.1 with enhanced features
• DOM Node APIs for native view access

Background: The Road to Architecture Unification

React Native’s New Architecture was introduced as a major overhaul to improve performance, reliability, and developer experience. In version 0.76, it became the default, but users could still fall back to the Legacy Architecture if needed.

After months of testing and refinement, the team now feels confident enough to make the New Architecture the only option. Future releases will focus on removing remaining legacy code to reduce app bundle size and streamline the codebase.

What This Means for Developers

For those still on the Legacy Architecture, migration is now urgent. The recommended path involves first moving to React Native 0.81 or Expo SDK 54, which are the last versions supporting both architectures. Developers should enable the New Architecture in 0.81 and verify their app works before upgrading to 0.82.

If a third-party dependency is blocking migration, the team advises contacting the library maintainers directly. For core bugs, developers should file issues in the React Native repository.

Interop Layers Remain Temporarily

To ease the transition, interop layers will be kept in the codebase for now. These layers ensure that third-party libraries that support both architectures will continue to function under 0.82. However, the team warns that future updates will address the eventual removal of these layers.

No Immediate Removal of Legacy APIs

To minimize breaking changes, React Native 0.82 does not remove any Legacy Architecture APIs from the core. The cleanup is scheduled for upcoming versions, starting with RFC0929, which aims to eliminate the remaining legacy code and reduce bundle size.

How to Upgrade to React Native 0.82

1. Update to React Native 0.81 or Expo SDK 54.
2. Enable the New Architecture and test thoroughly.
3. Once stable, upgrade to 0.82 to lock in the new architecture exclusively.

For more details, check the official release notes and migration guide.