React Native 0.80: Is It Time to Make the Switch?

3. More Accurate TypeScript Support (Experimental)

This release introduces an experimental Strict TypeScript mode. It's limited to React Native's public API but generates type definitions directly from the source code. This new support is currently experimental and opt-in, but it lays the groundwork for a more stable developer experience moving forward.

The new TypeScript types do not need to be maintained manually by the community; rather, they are automatically generated from React Native's source code. Furthermore, Types are now restricted to only what is exported from the main react-native package. Which means deep imports are deprecated and will trigger warnings.

To opt in you need to update your tsconfig.json to enable the Strict TypeScript API. Keep in mind that this is a one-time migration, but you can continue using the older types if you need more time to upgrade.

Examples

Before (Deprecated Deep Import):
import { Alert } from 'react-native/Libraries/Alert/Alert'; // Deprecated
After (Strict API):
import { Alert } from 'react-native'; // Recommended

4. Prebuilt Native Dependencies for iOS (Experimental)

Prebuilt native dependencies are compiled versions of third-party libraries that React Native relies on for iOS, such as Folly, GLog, and DoubleConversion. The latest version of React Native introduces a new feature that allows prebuilt native dependencies to be bundled into a reusable .xcframework.

This change is designed to drive the iOS development process faster and reliably. This feature ships certain third-party native libraries as prebuilt binaries, rather than requiring developers to build them from source.

Third-party dependencies can cause build failures or can take several minutes to complete. With prebuilt dependencies, initial iOS build times can be reduced and failures can be avoided, which leads to a more stable build process.

5. Clearer DevTools Warnings and React 19.1.0 Bump

React Native 0.80 now uses 19.1.0 and includes updates that improve the quality and clarity of warnings shown in DevTools. These warnings are more specific. For example, the warnings can be specific if it comes to deprecated APIs, missing architecture configurations, or outdated project setups.

This change can make the debugging process far less frustrating. With specific warnings, now you know where you to change or take action. It's a small change on the surface, but the cumulative effect is smoother workflows while working in the console or IDE.

6. JavaScriptCore (JSC) Support Handed Off to the Community

In React Native 0.80, official support for JavaScriptCore (JSC) as a bundled JavaScript engine has ended. Maintenance and updates for JSC are now handled by the community through the package @react-native-community/javascriptcore.

With JSC decoupled from React Native's release cycle, the community can provide updates, bug fixes, and improvements to JSC more rapidly and independently of React Native's core releases. If your project still relies on JSC, you must migrate to the community package or consider switching to Hermes, which remains the officially supported JavaScript engine for React Native.

React Native 0.80 Migration Guide: How to Upgrade Safely

To help you move forward, here’s a structured migration guide to safely upgrading React Native latest version.

1. Review the Official Upgrade Helper

Head over to the React Native upgrade helper. It's a web tool that compares your current version with the new one and shows the exact changes needed in files like package.json, android/build.gradle, Podfile, and others.

This tool ensures you don’t miss any subtle updates, like renamed properties or deprecated APIs.

2. Back Up Your Current Project

Always create a backup or commit your code to version control before starting the upgrade. If anything breaks during the process, you will be able to roll back quickly.

Use a separate Git branch for the migration and testing process.

3. Upgrade Dependencies in package.json

Update the core React Native dependencies:

npm install react-native@0.80.0 react@19.1.0

Or with Yarn:

yarn add react-native@0.80.0 react@19.1.0

After that, update related packages such as:

1. react-test-renderer

2. @react-native-community libraries

3. Any navigation, gesture, or animation libraries you’re using (check their changelogs for React Native 0.80 compatibility)

4. Clean and Reinstall Native Dependencies

Clear out old builds and dependencies to avoid cache-related errors:

# Remove node_modules and caches
rm -rf node_modules ios/Pods android/build
npm cache clean --force
# Reinstall
npm install
cd ios && pod install && cd ..

If you're upgrading to 0.80, it’s also a good time to evaluate your dependencies and consider modern UI libraries that fully support the latest features. This step is crucial to ensure that native changes (like updated Gradle or Xcode settings) take effect cleanly.

5. Align With the New Architecture (Optional but Recommended)

The React Native latest version continues building on the New Architecture foundations. If you haven’t migrated yet, now’s a good time to start enabling it using the opt-in flags in your project:

1. On Android: update gradle.properties to include newArchEnabled=true

2. On iOS: enable Fabric and TurboModules in your build configuration

This unlocks features like better startup performance, more predictable rendering, and tighter Hermes integration.

6. Handle Deprecated or Removed APIs

Check your terminal and DevTools for warnings about deprecated methods or configuration files. React Native 0.80, while not radically breaking, does clean up unused packages and encourages more modular code. Libraries or code that worked fine on older versions might need small adjustments.

7. Monitor for JSC Usage

Since JSC is no longer maintained by the React Native team starting from 0.80, double-check your project’s JavaScript engine. Hermes is now the recommended choice and comes enabled by default on new projects.

Expo users may notice fewer breaking changes and quicker access to updates, but it’s still important to understand the distinctions between React Native and Expo.

Should You Upgrade to React Native New Version?

If you are on an older version, then upgrading React Native to 0.80 is important for the long run. You don't need to immediately upgrade or rush into the new version of React Native. 

The decision to upgrade depends on where your app stands. If you're building something new or planning major feature work soon, now is a great time to upgrade.

The React Native latest version tightens the foundation for future updates. With improvements in debugging, support for React 19, updates to the Metro bundler, and stronger alignment with the New Architecture, this version focuses on making app development more predictable and scalable. If your existing app is stable but showing signs of lagging behind on dependencies or performance, React Native 0.80 offers a low-friction path to catch up. Staying current with the latest version is one of the best practices for scalable React Native apps, ensuring long-term maintainability and faster iteration cycles.

At Brilworks, we specialize in React Native development and modernization. If you want to build a reliable app from scratch or want expert guidance migrating to 0.80, our team can help you upgrade.