Introduction

React Native 0.80 has officially arrived, bringing a major version bump for the embedded React library to 19.1.0 and a series of changes aimed at stabilising the framework's JavaScript API. This release also marks the formal freezing of the Legacy Architecture and introduces warnings for APIs that will be removed in future versions. Developers get an early look at a stricter TypeScript API and an experimental improvement for iOS builds. Below we break down what's new and how to prepare.

React 19.1.0 Integration

The most straightforward upgrade in 0.80 is the update to React 19.1.0, the latest stable release of the core library. This brings React Native in sync with the newest React features, performance improvements, and bug fixes available in the broader React ecosystem. No additional migration steps are required beyond updating your React Native version, but you should verify that your third-party dependencies are compatible with React 19.

Changes to the JavaScript Public API

React Native 0.80 takes two important steps toward a more stable and well-defined public API: deprecating deep imports and offering an opt-in strict TypeScript API.

Deprecation of Deep Imports

Deep imports — accessing internal modules via paths like react-native/Libraries/Alert/Alert — are now formally deprecated. Starting with 0.80, ESLint and the JavaScript console will show warnings when your project uses such imports. The goal is to reduce the surface area of the public API and ensure that only stable, supported exports are accessible.

The recommended replacement is to use the root import:

// Before (deprecated)
import {Alert} from 'react-native/Libraries/Alert/Alert';

// After (preferred)
import {Alert} from 'react-native';

Some APIs that were only available via deep imports will become completely inaccessible. This is intentional and will be finalised over the upcoming releases. The team has opened a feedback thread for developers to report issues and discuss which APIs should remain publicly exported.

Opt-in Strict TypeScript API

Alongside the existing TypeScript types, React Native 0.80 introduces a Strict TypeScript API that developers can opt into via their tsconfig.json. These types are generated directly from the source code, resulting in better coverage, accuracy, and stronger compatibility guarantees. They are also restricted to the package's index file, meaning internal file changes won't break your code.

To enable it, add a compiler option in your tsconfig.json (details included in the release notes). Most apps that use standard React Native APIs should validate immediately without changes. Early adopters and new projects are strongly encouraged to try this stricter type setting.

Legacy Architecture Freezing

As part of the ongoing migration to the new architecture, the Legacy Architecture is now officially frozen. No new features or non-critical bug fixes will be applied to it. Starting in 0.80, you will see warnings when using APIs that depend on the legacy internals. These warnings are a heads-up that such APIs will stop working once the legacy architecture is fully removed in a future major release.

Developers still on the legacy architecture should plan to migrate to the new architecture (also known as Fabric + TurboModules) as soon as possible. The warnings serve as a guide to identify code that needs to be updated.

Experimental: Prebuilt iOS Dependencies

For iOS developers, React Native 0.80 ships an experimental improvement: prebuilt iOS dependencies. Instead of compiling all native libraries from source each time, you can now download them prebuilt. This can significantly reduce build times during development and CI. To test this feature, follow the experimental instructions in the release notes. Feedback is welcome as the team refines the approach for future inclusion by default.

How to Prepare for Upcoming Changes

Migrating from Deep Imports

Review your codebase for any import paths under react-native/Libraries/ or react-native/private/. Replace them with the equivalent exports at the root level. If an API is missing from the root, check the feedback thread to see if it's being considered for re‑export. Use the ESLint plugin provided by React Native to catch these automatically.

Adopting the Strict TypeScript API

Update your tsconfig.json to enable the strict types. Run your type checker and fix any new errors. Because the new types are generated from source, you may encounter stricter checks — but this is a good opportunity to improve type safety. If you encounter missing types for community libraries, consider temporarily reverting until those libraries update.

Also monitor the React Native changelog for further deprecation warnings and migration guides.

Conclusion

React Native 0.80 is a stability‑focused release that paves the way for a cleaner, more predictable JavaScript API. By upgrading, you gain React 19.1, a preview of strict TypeScript types, and a clear timeline for the legacy architecture's retirement. Start by fixing deep import warnings and experimenting with the strict types to ensure a smooth transition to future versions.