React Native 0.80 is rolling out two major changes to its JavaScript API that signal a shift toward a more stable and type-safe development experience. The update deprecates deep imports from the react-native package and introduces an opt-in Strict TypeScript API, marking the beginning of a long-term effort to formally define the framework's public interface.
Immediate action required for developers: Deep imports—such as import {Alert} from 'react-native/Libraries/Alert/Alert'—now trigger deprecation warnings in ESLint and the JavaScript console. Developers are urged to migrate to root imports like import {Alert} from 'react-native'. The team plans to remove deep import paths entirely in React Native 0.82.
Meanwhile, an opt-in Strict TypeScript API provides stronger type accuracy and a new public API baseline generated directly from React Native's source code. This is a one-time breaking change designed to future-proof typings, and it is enabled via compilerOptions in tsconfig.json.
Background
React Native's JavaScript API has historically been loosely defined. The framework is authored in Flow, but the developer ecosystem overwhelmingly uses TypeScript. Community-contributed types, while appreciated, lacked automated tooling and introduced correctness gaps. Additionally, internal paths like react-native/Libraries/ were accessible from app code but changed with internal updates, creating instability.
According to the React Native team, these issues have made it difficult to guarantee API stability. The 0.80 release directly addresses both problems: deprecating deep imports reduces the surface area to a controlled set of exports, while the Strict TypeScript API provides a verified baseline.
What This Means
For developers, this is a transitional phase. The deprecation warnings give time to update imports, but the eventual removal of deep imports will break code that relies on them. A feedback thread has been opened for APIs not yet exposed at root level.
The Strict TypeScript API is currently opt-in, but the team plans to enable it by default in a future release. This will enforce stricter type checking and align React Native's public API with modern TypeScript practices. Experts see this as a necessary step to reduce fragmentation and improve library compatibility.
“These changes represent the groundwork for a stable React Native API that developers can rely on across versions,” said a React Native core contributor. “We're working with the community to finalize the export list before making the Strict TypeScript API the default.”
In summary, React Native 0.80 requires immediate attention from developers using deep imports and offers a preview of the type-safe future. The full transition is expected over the next two releases.