Remove unused types/*.d.ts export subpath#57362
Closed
huntie wants to merge 1 commit into
Closed
Conversation
Summary: The `"./types/*.d.ts"` entry was an overly defensive addition during our non-breaking `"exports"` field addition back in 0.80. In reality, this subpath has no real consumers: the legacy types entry point (`.`) resolves its own declaration files through relative references, and the supported deep-import surface is `react-native/Libraries/*`, not `react-native/types/*`. Type resolution of the main entry point and of `react-native/Libraries/*` deep imports is unaffected, and there is no runtime impact (these are declaration files). Follows the exports-map cleanup in react#57276. Changelog: [Internal] Differential Revision: D110044754
meta-cla
Bot
added
the
CLA Signed
|
@huntie has exported this pull request. If you are a Meta employee, you can view the originating Diff in D110044754. |
|
This pull request has been merged in 8638a19. |
meta-codesync Bot
pushed a commit
that referenced
this pull request
Jun 29, 2026
Summary: Pull Request resolved: #57366 Follows #57362 (accidentally missed). Simplifying our `"exports"` map to its minimum form will help for the incoming review/understandability of the Strict TS API rollout by default. Changelog: [Internal] landed-with-radar-review Reviewed By: robhogan Differential Revision: D110055788 fbshipit-source-id: 83919aec45f3be18c08e983a751de1117c237171
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
The
"./types/*.d.ts"entry was an overly defensive addition during our non-breaking"exports"field addition back in 0.80.In reality, this subpath has no real consumers: the legacy types entry point (
.) resolves its own declaration files through relative references, and the supported deep-import surface isreact-native/Libraries/*, notreact-native/types/*.Type resolution of the main entry point and of
react-native/Libraries/*deep imports is unaffected, and there is no runtime impact (these are declaration files).Follows the exports-map cleanup in #57276.
Changelog: [Internal]
Differential Revision: D110044754