From cf0effcf9cb21cc693d91a97ccf0cb5a14f37f5d Mon Sep 17 00:00:00 2001 From: Floyd Kim Date: Sat, 14 Jun 2025 20:36:23 +0900 Subject: [PATCH] Update 2025-06-12-react-native-0.80.md --- website/blog/2025-06-12-react-native-0.80.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/2025-06-12-react-native-0.80.md b/website/blog/2025-06-12-react-native-0.80.md index 4b12a6d36be..baaa27fdaa5 100644 --- a/website/blog/2025-06-12-react-native-0.80.md +++ b/website/blog/2025-06-12-react-native-0.80.md @@ -30,7 +30,7 @@ Moreover, the Legacy Architecture of React Native is now officially frozen, and In this release, we are making moves to improve and stabilize React Native's public JavaScript API. The first step towards this is better scoping of which of our APIs are importable by apps and frameworks. In line with this, we are formally deprecating deep imports from React Native ([see RFC](https://github.com/react-native-community/discussions-and-proposals/pull/894)), and are introducing warnings via ESLint and the JS console. -These warnings are scoped to imports from within your project's source code, and can be [opted out from](/docs/strict-typescript-api). However, please bear in mind that we aim to remove deep imports from React Native's API in a future release, and these should instead be updated to the root import. +These warnings are scoped to imports from within your project's source code, and can be [opted out from](https://reactnative.dev/blog/2025/06/12/moving-towards-a-stable-javascript-api#deprecating-deep-imports-from-react-native). However, please bear in mind that we aim to remove deep imports from React Native's API in a future release, and these should instead be updated to the root import. ```js // Before - import from subpath