React Native 0.82 marks a pivotal moment as the first version to operate solely on the New Architecture. This release solidifies the architectural shift started in 0.76 and introduces experimental upgrades like Hermes V1 and React 19.1.1 with DOM Node API support. Below, we explore the key changes and what they mean for developers.
What does "New Architecture Only" mean in React Native 0.82?
This version fully commits to the New Architecture, making it the sole engine for running React Native apps. Attempts to revert to the Legacy Architecture via flags like newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS are now ignored. The legacy code remains present but inactive, ensuring backward compatibility for libraries that still rely on interop layers. This decisive move follows the successful defaulting in 0.76 and extensive real-world testing. Future versions will remove legacy classes entirely to shrink bundle size. For teams still on the old architecture, it is critical to migrate now—start with version 0.81 or Expo SDK 54, enable the New Architecture, verify stability, then upgrade to 0.82.
How can developers safely migrate to React Native 0.82?
Migration follows a clear path: first upgrade to React Native 0.81 or Expo SDK 54, which are the last versions that allow Legacy Architecture usage. Enable the New Architecture in that version and thoroughly test your application, paying attention to performance and third-party library behavior. Once everything works, update to 0.82, which automatically enforces the New Architecture. If a third-party dependency blocks migration, reach out directly to its maintainers. For bugs in React Native core, report them via the project's issue tracker. The interop layers remain active temporarily, so libraries that offer backward compatibility will still function.
What is the experimental Hermes V1 support?
React Native 0.82 includes an optional, experimental upgrade to Hermes V1, a newer version of the JavaScript engine. This engine promises better performance and lower memory usage. It is not enabled by default—developers must opt in by adjusting project configuration. This allows early adopters to test the engine in real-world scenarios and provide feedback. The team plans to refine Hermes V1 based on community input before making it the default in a future release. If you are interested in improving startup times and runtime efficiency, consider enabling this experiment in your development builds.
How does React 19.1.1 and DOM Node APIs benefit developers?
Updating React to version 19.1.1 brings the latest React features and bug fixes to React Native. One notable addition is support for DOM Node APIs, which allow developers to programmatically access and manipulate native UI elements. This bridges the gap between web and mobile development patterns, enabling more direct control over the rendering tree. For example, you can now use standard DOM methods to interact with native components, simplifying code reuse and migration from web projects. These APIs are especially useful for libraries that need fine-grained access to the underlying view hierarchy.
Will existing third-party libraries continue to work?
Yes, libraries that previously supported both architectures will continue to function in React Native 0.82. The interop layers that translate between Legacy and New Architecture are preserved for the foreseeable future, ensuring backward compatibility. However, library maintainers are strongly encouraged to fully adopt the New Architecture to benefit from performance improvements and future-proof their code. If you encounter issues with a specific library, contact its maintainers directly—most are already updating to align with the new architecture. The React Native core team will share further updates before removing the interop layers entirely.
When will the Legacy Architecture code be removed?
Removal of the Legacy Architecture code is scheduled to begin in the next major version after 0.82. This release deliberately does not remove any APIs to minimize breaking changes and give developers time to adapt. Once removed, the bundle size will decrease significantly as legacy classes and functions are no longer included. Detailed plans are outlined in RFC0929: Removal of the Legacy Architecture of React Native. Developers are advised to complete their migration now to avoid disruptions when the removal happens. The interoperabillity layers will be removed later, but the transition period is designed to be smooth.