Introduction
With the release of React Native 0.80, the framework takes a major step toward a more stable and dependable JavaScript API. Two key changes are being introduced: the deprecation of deep imports and an opt-in Strict TypeScript API. These updates are part of an ongoing effort to clearly define the public API surface, reduce accidental usage of internal modules, and provide robust type safety for developers and third-party libraries.
Why These Changes Matter
React Native’s JavaScript API has historically been somewhat loosely defined. The framework is authored in Flow, while the community has overwhelmingly adopted TypeScript. As a result, the type definitions available to developers were manually maintained and community-contributed, leading to gaps in correctness. Furthermore, the public API lacked strict module boundaries — internal packages like react-native/Libraries/ were accessible through deep imports, but these paths could change without notice as internal code evolved.
By addressing these issues now, React Native lays the groundwork for a stable, predictable API that will reduce breaking changes in future releases and improve the developer experience.
Key Changes in 0.80
1. Deprecation of Deep Imports
Starting with version 0.80, deep imports from the react-native package are deprecated. Developers will see warnings both in ESLint and the JavaScript console when they use paths like react-native/Libraries/Alert/Alert. Instead, all exports should be accessed from the root import: import { Alert } from 'react-native';.
This change reduces the total surface area of the API to a fixed set of exports that React Native can control and stabilize. The plan is to completely remove support for deep import paths in version 0.82.
What If an API Is Not Exported at Root?
Some APIs currently only available via deep imports will become inaccessible once the removal is complete. The React Native team has opened a feedback thread to hear from the community about which missing exports should be added to the root API. Developers are encouraged to share their use cases so that the public API can be finalized appropriately.
How to Opt Out
If you rely on deep imports that are not yet available at root, you may temporarily suppress the deprecation warnings, but note that these paths will be removed in 0.82. The recommended action is to migrate all imports to the root module as soon as possible.
2. Opt-In Strict TypeScript API
React Native 0.80 introduces a new generated TypeScript baseline — the Strict TypeScript API. This is an opt-in feature that provides more accurate and future-proof type definitions directly from the React Native source code, rather than relying on manually maintained types.
To enable it, developers add a compilerOptions entry in their project’s tsconfig.json — specific instructions are provided in the official documentation. Once activated, the new types will replace the previous community-contributed ones. This is a one-time breaking change: code that relied on previously incorrect or missing type definitions may need adjustment.
Benefits of the Strict TypeScript API
- Stronger type accuracy — types are auto-generated from the actual source code, eliminating manual maintenance gaps.
- Better alignment with the community — the ecosystem already uses TypeScript, so this change brings the framework in line with developer expectations.
- Future stability — the new baseline will make it easier to maintain backward compatibility in upcoming versions.
Working Together During the Transition
The React Native team is committed to collaborating with the community to ensure these changes work smoothly for everyone. The Strict TypeScript API will remain opt-in for now, and deep imports will continue to function (with warnings) through version 0.81. The default setting will switch to the Strict TypeScript API in a future release after gathering feedback and addressing any issues.
Summary of Changes
- Deep imports deprecated — use root exports from
react-nativeinstead. Removal targeted for 0.82. - Strict TypeScript API — opt in via
tsconfig.jsonfor more accurate types. Will become default later. - Community feedback welcome on missing root exports and type accuracy issues.
Next Steps for Developers
If you’re using React Native 0.80 or planning to upgrade, take these actions:
- Run your linter and look for deep import warnings — replace them with root imports.
- If you use TypeScript, enable the Strict TypeScript API in your
tsconfig.jsonand review any type errors that arise. - Check the feedback thread for APIs you need that are not yet exported at root, and submit your input.
These changes mark a significant improvement in the stability and reliability of React Native’s JavaScript API, making it easier to build and maintain cross-platform applications.