How to Upgrade to React Native 0.82: Embracing the New Architecture

By ✦ min read

Introduction

React Native 0.82 marks a pivotal shift in mobile development. It’s the first version that runs entirely on the New Architecture, leaving behind the legacy system that powered React Native for years. This guide walks you through upgrading your project to this milestone release, ensuring you can take full advantage of its improvements—like reduced bundle size, better performance, and experimental features such as Hermes V1 and React 19.1.1.

By following these steps, you’ll migrate safely from older versions, handle third-party library compatibility, and unlock new possibilities like DOM Node APIs. Let’s begin.

What You Need

• An existing React Native project (preferably on version 0.81 or Expo SDK 54).
• Node.js (v18 or later) and npm/yarn installed.
• Basic familiarity with React Native CLI and package management.
• Access to your project’s android/ and ios/ directories.
• Time to test thoroughly after each step.

Step-by-Step Upgrade Guide

Step 1: Migrate to React Native 0.81 (or Expo SDK 54)

Before moving to 0.82, you must be on a version that still supports the Legacy Architecture as a fallback. The recommended base is React Native 0.81 (or Expo SDK 54). This version includes deprecation warnings and performance tweaks that ease the transition to the New Architecture.

• If you’re on an older React Native version, upgrade incrementally using the official upgrade helper (npx react-native upgrade) or by following the changelog.
• For Expo projects, run expo upgrade to move to SDK 54.

Once on 0.81/54, verify your app builds and runs correctly.

Step 2: Enable the New Architecture in 0.81

React Native 0.81 made the New Architecture the default, but you can still revert to the Legacy Architecture if needed. To ensure a smooth transition, explicitly enable the New Architecture and test your app.

• For Android: set newArchEnabled=true in android/gradle.properties.
• For iOS: set RCT_NEW_ARCH_ENABLED=1 before running pod install (e.g., RCT_NEW_ARCH_ENABLED=1 pod install).

Now rebuild and run your app. Watch for any issues with native modules or third-party libraries. The New Architecture uses JSI and Fabric, so some libraries may require updated versions.

Step 3: Test Your App with the New Architecture

Thorough testing is critical. Run your app on both iOS and Android simulators and physical devices. Check:

• All screens and navigation flows.
• Third-party libraries (e.g., maps, camera, gestures).
• Performance under load (use React DevTools or Flipper).

If you encounter a bug in React Native core, report it on the issue tracker. For incompatible third-party libraries, contact the maintainers. You can also rely on the interop layers that React Native 0.82 still provides, but it’s best to fix compatibility now.

Step 4: Upgrade to React Native 0.82

Once you’re confident on 0.81 with the New Architecture, it’s time to move to 0.82. Run:

npx react-native upgrade 0.82.0

Or update your package.json manually and run npm install. Then reinstall pods (cd ios && pod install) and update Android Gradle files if needed.

Important: In 0.82, the New Architecture is enforced—newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS are ignored. The Legacy Architecture classes remain in the codebase for now, but they won’t be used.

Step 5: Handle Third-Party Libraries

React Native 0.82 keeps the interop layers to ensure backward compatibility with libraries that support both architectures. These layers will remain for the foreseeable future, but you should strive to use libraries that are fully aligned with the New Architecture.

• Check each library’s documentation for New Architecture support.
• If a library uses outdated native APIs, reach out to its maintainers.
• The interop layers cover most classes and functions needed by legacy libraries, so your app should work.

Step 6: Opt In to Experimental Hermes V1

React Native 0.82 ships with an experimental version of Hermes called Hermes V1. To try it:

• Set hermesVersion in your project configuration to the experimental V1 release (see official docs for exact version).
• Alternatively, wait for the stable release if you prefer caution.

Hermes V1 brings improved startup time and memory efficiency. Test thoroughly if you enable it.

Step 7: Leverage New Features

With 0.82, you get React 19.1.1 (enabling newer React features) and DOM Node APIs (for direct node manipulation). Update your components to take advantage:

• Use useRef and createRef with DOM Node APIs for better performance in animations or custom views.
• Explore React 19 features like useOptimistic or improved useTransition.

Refer to the React 19 changelog and React Native 0.82 release notes for full details.

Tips & Conclusion

• Don’t skip testing: The New Architecture changes how native modules interact, so regression testing is vital.
• Plan for future removals: Starting with the next React Native version (0.83), the Legacy Architecture classes will be removed, reducing bundle size. Prepare your libraries now.
• Use the interop layers as a bridge: They’re safe for now, but don’t rely on them long-term.
• Monitor performance: Run benchmarks before and after the upgrade to quantify improvements.
• Reach out for help: If blocked by a core bug, open an issue on the React Native GitHub. For third-party libraries, contact maintainers directly.

Upgrading to React Native 0.82 puts you at the forefront of mobile development. The New Architecture alone delivers faster JavaScript-native communication and a leaner codebase. Combined with experimental Hermes V1 and React 19, your apps will be more efficient and easier to maintain. Welcome to the new era of React Native.