Inline the last duplicate Platform.select key - #58249
Closed
OskarEichler wants to merge 1 commit into
Closed
Conversation
robhogan
approved these changes
Aug 31, 2026
Contributor
|
Let's discuss this at react/metro#1889. |
|
@vzaidman has imported this pull request. If you are a Meta employee, you can view this in D118499490. |
meta-codesync Bot
pushed a commit
to react/metro
that referenced
this pull request
Sep 4, 2026
Summary:
Metro statically replaces `Platform.select({...})` for the target platform. Its property scan currently stops at the first matching key, while JavaScript object-literal evaluation keeps the last duplicate definition. For example, `Platform.select({ios: 1, ios: 2})` runs as `2` but Metro compiles it to `1`.
Scan the already-validated static properties from the end and return the first reverse match. This preserves O(n) behavior, avoids an unnecessary nullable temporary, and keeps compiled output consistent with runtime object semantics. The React Native Babel preset contains a parallel transform; companion [React Native PR #58249](react/react-native#58249) applies the same rule there.
Changelog:
```
- **[Fix]**: Inline the last duplicate key from static `Platform.select` object literals
```
Pull Request resolved: #1889
Test Plan:
- Added a focused `metro-transform-plugins` regression; it fails on pristine main with `1` and passes with `2` after the fix.
- All package suites pass: 6/6 suites, 160/160 tests, 41 snapshots.
- Full Flow check reports no errors.
- Full monorepo build passes for all 17 packages.
- Targeted ESLint, Prettier, and `git diff --check` pass.
No behavior changes for object literals without duplicate static keys.
Reviewed By: GijsWeterings
Differential Revision: D118499357
Pulled By: vzaidman
fbshipit-source-id: 1036c78826c4e7d12a94baa8b8eeb1a04f9f8f60
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
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 React Native Babel preset statically replaces
Platform.select({...})for the target platform. Its property scan currently stops at the first matching key, while JavaScript object-literal evaluation keeps the last duplicate definition. For example,Platform.select({ios: 1, ios: 2})runs as2but the preset compiles it to1.Scan the already-validated static properties from the end so compiled output matches runtime semantics while preserving O(n), allocation-free lookup. Metro has a parallel transform that can run first; companion Metro PR #1889 applies the same correction so output remains transform-order independent.
Changelog:
[GENERAL] [FIXED] - Inline the last duplicate key from static Platform.select object literals.
Test Plan:
const value=1, while the fix emitsconst value=2.git diff --checkpass.No behavior changes for object literals without duplicate static keys; no UI change.