Skip to content

Commit f9808f3

Browse files
committed
improved texts
1 parent 0c5be52 commit f9808f3

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

website/blog/2025-10-08-react-native-0.82.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'React Native 0.82 - New Architecture Only, React 19.1.1, Hermes V1, DOM Node APIs, and more'
2+
title: 'React Native 0.82 - New Architecture Only'
33
authors: [vzaidman, cortinico, gabrieldonadel, alanjhughes]
44
tags: [engineering]
55
date: 2025-10-08
@@ -8,11 +8,12 @@ date: 2025-10-08
88
import Tabs from '@theme/Tabs';
99
import TabItem from '@theme/TabItem';
1010

11-
# **React Native 0.82 - New Architecture Only, Experimental Hermes V1, React 19.1.1, DOM Node APIs, and more!**
11+
# **React Native 0.82 - New Architecture Only**
1212

13-
Today we are excited to release React Native 0.82!
13+
Today we're exited to release React Native 0.82: the first React Native release that removes the legacy architecture and runs entirely on the New Architecture.
14+
<br/> This is a milestone release for React Native and we believe it's the start of a new era. In future versions we will be removing the remaining code from the legacy architecture to reduce install size and streamline the codebase.
1415

15-
This release is a crucial milestone for React Native: after multiple years of rollout of the New Architecture, we’re finally sunsetting the Legacy Architecture. The New Architecture is now the **only** architecture of React Native. This release also ships with a newer version of our JavaScript engine: Hermes V1, which is available via an experimental opt-in. We’re also updating the React version to 19.1.1 and shipping support for DOM Node APIs.
16+
This release also ships with a newer version of our JavaScript engine: Hermes V1, which is available via an experimental opt-in. We’re also updating the React version to 19.1.1 and shipping support for DOM Node APIs.
1617

1718
### Highlights
1819

@@ -27,21 +28,19 @@ This release is a crucial milestone for React Native: after multiple years of ro
2728

2829
## New Architecture Only
2930

30-
Starting with this version, [the New Architecture](https://reactnative.dev/blog/2024/10/23/the-new-architecture-is-here) will be the **only** architecture for React Native, there will no longer be an option to opt-out of the New Architecture.
31+
In React Native 0.76 we announced that [The New Architecture was here](/blog/2024/10/23/the-new-architecture-is-here) and enabled by default. Since then, the New Architecture has been tested and refined and we're confident in making it the only architecture.
3132

32-
The New Architecture has been tested and refined over a long period of time, and [has been the default architecture since version 0.76](https://reactnative.dev/blog/2024/10/23/the-new-architecture-is-here). We're now confident in making it the only architecture.
33+
Starting today, new versions of React Native will **only** run with the New Architecture. This means, if you try to set `newArchEnabled=false` on Android, or if you try to install CocoaPods with `RCT_NEW_ARCH_ENABLED=0` on iOS, these will be ignored and your app will still run with the New Architecture enabled.
3334

34-
In 0.82, if you try to set `newArchEnabled=false` on Android, or if you try to install CocoaPods with `RCT_NEW_ARCH_ENABLED=0` on iOS, these will be ignored and your app will still run with the New Architecture enabled.
35+
To learn more about the New Architecture, see [The New Architecture was here](/blog/2024/10/23/the-new-architecture-is-here).
3536

3637
### How to migrate
3738

38-
If you haven’t migrated your project to the New Architecture, our recommendations are the following:
39+
If you haven’t migrated your project to the New Architecture, we recommendation first migrating your project to React Native 0.81 or Expo SDK 54. These are the last versions that allow you to opt-in to the Legacy Architecture. They contain warning and performance improvements specifically to help migrating to the New Architecture.
3940

40-
First, migrate your project to React Native 0.81 or Expo SDK 54. Those are the last versions that support the opt-out and contain various performance improvements specifically for users migrating to the New Architecture.
41+
Once you're using the New Architecture in 0.81, you can update safely to React Native 0.82 which removes the legacy achitecture.
4142

42-
Then enable the New Architecture in 0.81 and verify that your application is working fine.
43-
44-
You can then update safely to React Native 0.82 and future versions.
43+
#### Issues migrating
4544

4645
If an incompatible 3rd party dependency prevents you from migrating to the New Architecture, we recommend you reach out to the library maintainers directly.
4746

@@ -56,7 +55,6 @@ We’ve also verified that the 3P libraries that offer backward compatibility wi
5655
### Removal of Legacy Architecture classes
5756

5857
To ensure backward compatibility and reduce breaking changes, we are not removing any APIs of the Legacy Architecture from the core of React Native in this version.
59-
6058
Removing the Legacy Architecture will allow us to save significant size on the overall bundle size, therefore the removal is scheduled to start from the next version of React Native.
6159

6260
You can find more information in [RFC0929: Removal of the Legacy Architecture of React Native](https://github.com/react-native-community/discussions-and-proposals/pull/929).

0 commit comments

Comments
 (0)