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
Copy file name to clipboardExpand all lines: website/blog/2025-06-12-moving-towards-a-stable-javascript-api.mdx
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ In React Native 0.80, we're introducing two significant changes to React Native'
10
10
**Quick takeaways:**
11
11
12
12
-**Deep imports deprecation**: From 0.80, we're introducing deprecation warnings for deep imports from the `react-native` package.
13
-
-**Opt-in Strict TypeScript API**: We are moving to from-source TypeScript types and a new public API baseline under TypeScript. These enable stronger and more futureproof type accuracy, and will be a one-time breaking change. [Opt in](/blog/2025/06/12/moving-towards-a-stable-javascript-api#strict-typescript-api) via `compilerOptions` in your project's `tsconfig.json`.
13
+
-**Opt-in Strict TypeScript API**: We are moving to from-source TypeScript types and a new public API baseline under TypeScript. These enable stronger and more futureproof type accuracy, and will be a one-time breaking change. [Opt in](/blog/2025/06/12/moving-towards-a-stable-javascript-api#future--strict-typescript-api-by-default) via `compilerOptions` in your project's `tsconfig.json`.
14
14
- We'll work with the community over time to ensure that these changes work for everyone, before enabling the Strict TypeScript API by default in a future React Native release.
15
15
16
16
{/* truncate */}
@@ -310,20 +310,20 @@ Thanks also to [Pieter Vanderwerff](https://github.com/pieterv), [Rubén Norte](
0 commit comments