diff --git a/docs/strict-typescript-api.md b/docs/strict-typescript-api.md index 86539775e61..38e07387e53 100644 --- a/docs/strict-typescript-api.md +++ b/docs/strict-typescript-api.md @@ -32,7 +32,7 @@ Opting in is a **breaking change**, since some of our new types have updated nam :::note Under the hood -This will instruct TypeScript to resolve `react-native` types from our new [`types_generated/`](https://www.npmjs.com/package/react-native?activeTab=code) dir, instead of the previous [`types/`](https://www.npmjs.com/package/react-native?activeTab=code) dir (manually maintained). No restart of TypeScript or your text editor is required. +This will instruct TypeScript to resolve `react-native` types from our new [`types_generated/`](https://www.npmjs.com/package/react-native?activeTab=code) dir, instead of the previous [`types/`](https://www.npmjs.com/package/react-native?activeTab=code) dir (manually maintained). No restart of TypeScript or your editor is required. ::: @@ -42,7 +42,7 @@ The Strict TypeScript API follows our [RFC](https://github.com/react-native-comm **Sending feedback**: We will be working with the community to finalize which APIs we export over (at least) the next two React Native releases. Please share your feedback in our [feedback thread](https://github.com/react-native-community/discussions-and-proposals/discussions/893). -See also our announcement blog post (incoming) for more info on our motivation and timelines. +See also our [announcement blog post](/blog/2025/06/12/moving-towards-a-stable-javascript-api) for more info on our motivation and timelines. ::: diff --git a/website/blog/2025-06-12-moving-towards-a-stable-javascript-api.md b/website/blog/2025-06-12-moving-towards-a-stable-javascript-api.md index 4f9f8a9e238..7699bf46e87 100644 --- a/website/blog/2025-06-12-moving-towards-a-stable-javascript-api.md +++ b/website/blog/2025-06-12-moving-towards-a-stable-javascript-api.md @@ -10,7 +10,7 @@ In React Native 0.80, we're introducing two significant changes to React Native' **Quick takeaways:** - **Deep imports deprecation**: From 0.80, we're introducing deprecation warnings for deep imports from the `react-native` package. -- **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/09/moving-towards-a-stable-javascript-api#strict-typescript-api) via `compilerOptions` in your project's `tsconfig.json`. +- **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`. - 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. @@ -152,7 +152,7 @@ When the community is ready, the Strict TypeScript API will become our default A :::note Under the hood -This will instruct TypeScript to resolve `react-native` types from our new [`types_generated/`](https://www.npmjs.com/package/react-native?activeTab=code) dir, instead of the previous [`types/`](https://www.npmjs.com/package/react-native?activeTab=code) dir (manually maintained). No restart of TypeScript or your text editor is required. +This will instruct TypeScript to resolve `react-native` types from our new [`types_generated/`](https://www.npmjs.com/package/react-native?activeTab=code) dir, instead of the previous [`types/`](https://www.npmjs.com/package/react-native?activeTab=code) dir (manually maintained). No restart of TypeScript or your editor is required. :::