You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the RFC | See the 0.80 release post (incoming)
🚨 Key change: In React Native 0.80, we are deprecating subpath imports (or "deep imports") from the react-native npm package.
By defining a clear, root-level JavaScript API contract, we aim to minimise future React Native breaking changes and improve long-term predictability for the ecosystem.
// Before - subpath imports allowedimport{Alert,AlertType}from'react-native/Libraries/Alert/Alert';// After - must import from 'react-native'import{Alert,AlertType}from'react-native';
Why it matters: While initially deprecated with warnings, we aim to remove these import paths entirely, which will be a breaking change.
This discussion thread
Please raise issues/questions about APIs you are using that are affected by this change. Over our API consultation period (beginning 0.80), we'll evaluate requests for exposing new APIs at the root, or providing alternatives.
Planned sequencing
React Native 0.80: Deprecation of subpath imports, introduce runtime warnings.
React Native 0.82 (or later): Removal of subpath imports via "exports" and the Strict TypeScript API.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Introduction
See the RFC | See the 0.80 release post (incoming)
🚨 Key change: In React Native 0.80, we are deprecating subpath imports (or "deep imports") from the
react-native
npm package.By defining a clear, root-level JavaScript API contract, we aim to minimise future React Native breaking changes and improve long-term predictability for the ecosystem.
Why it matters: While initially deprecated with warnings, we aim to remove these import paths entirely, which will be a breaking change.
This discussion thread
Please raise issues/questions about APIs you are using that are affected by this change. Over our API consultation period (beginning 0.80), we'll evaluate requests for exposing new APIs at the root, or providing alternatives.
Planned sequencing
"exports"
and the Strict TypeScript API.Beta Was this translation helpful? Give feedback.
All reactions