Expose unstable_NativeText and unstable_NativeView components #53777
+29
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
meta-cla
bot
added
the
CLA Signed
huntie
added
the
JS API refinements (2025)
…ok#53777) Summary: Expose `unstable_NativeText` and `unstable_NativeView` components as root exports of the `react-native` package. These are exposed as `unstable_` APIs which have no semver guarantee. **Motivation** There is significant community interest / dependance on the currently private `TextNativeComponent` and `ViewNativeComponent` deep imports, to access the faster-performing inner versions of these UI components. Using `<Text>` and `<View>`, while recommended and stable, has led to measurable performance overhead in some apps when compared with these `<Native*>` counterparts. Notably, these APIs are also referenced by low-level libraries such as React Strict DOM. I am proposing this change in order to: - Unblock libraries which safely use these. - Meet users where they are at. - Unblock us from enabling the Strict TypeScript API (no deep imports). References: - react-native-community/discussions-and-proposals#893 (comment) - https://javascript.plainenglish.io/optimizing-text-component-rendering-in-react-native-b9d3565659d9 - https://github.com/search?type=code&q=react-native%2FLibraries%2FText%2FTextNativeComponent **Ideal future state** We are exposing these as unstable APIs because they should not be part of React Native's final API. The ideal end state is we improve the regular `<Text>` and `<View>` components to eliminate performance overhead and the need to access any lower level API. Changelog: [General][Added] - `unstable_NativeText` and `unstable_NativeView` are now exported from the `react-native` package Reviewed By: javache Differential Revision: D81588145
huntie
force-pushed
the
export-D81588145
branch
from
71d58de to
cf97aed
Compare
|
This pull request has been merged in 90ac3ac. |
|
This pull request was successfully merged by @huntie in 90ac3ac When will my fix make it into a release? | How to file a pick request? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Expose
unstable_NativeTextandunstable_NativeViewcomponents as root exports of thereact-nativepackage.These are exposed as
unstable_APIs which have no semver guarantee.Motivation
There is significant community interest / dependance on the currently private
TextNativeComponentandViewNativeComponentdeep imports, to access the faster-performing inner versions of these UI components.Using
<Text>and<View>, while recommended and stable, has led to measurable performance overhead in some apps when compared with these<Native*>counterparts.Notably, these APIs are also referenced by low-level libraries such as React Strict DOM.
I am proposing this change in order to:
References:
Ideal future state
We are exposing these as unstable APIs because they should not be part of React Native's final API. The ideal end state is we improve the regular
<Text>and<View>components to eliminate performance overhead and the need to access any lower level API.Changelog:
[General][Added] -
unstable_NativeTextandunstable_NativeVieware now exported from thereact-nativepackageReviewed By: javache
Differential Revision: D81588145