Skip to content

Fix: platform inline transformation#1521

Open
IvanIhnatsiuk wants to merge 2 commits intofacebook:mainfrom
IvanIhnatsiuk:fix/inline-platform-transformation
Open

Fix: platform inline transformation#1521
IvanIhnatsiuk wants to merge 2 commits intofacebook:mainfrom
IvanIhnatsiuk:fix/inline-platform-transformation

Conversation

@IvanIhnatsiuk
Copy link

Summary

I noticed that when using esmodule named import of platform dead code elimination of Platform.OS did not work.

In this PR, I added logic to find to check that Platform.OS was used from require('react-native). That way, it doesn't matter what name the react-native import has.

Changelog:

Before:

import { Platform } from 'react-native';

if (Platform.OS === 'android') {
  // code
}

Transformed:

import { Platform } from 'react-native';

var _reactNative = _$$_REQUIRE(_dependencyMap[4]);

if (_reactNative.Platform.OS !== 'android') {
  // code
}

After:

import { Platform } from 'react-native';

if (Platform.OS === 'android') {
  // code
}

Transformed:

import { Platform } from 'react-native';

var _reactNative = _$$_REQUIRE(_dependencyMap[4]);

if ('android' !== 'android') {
  // code
}

Test plan

Added a test for the case similar to how code looks in the transformed bundle before being passed to the inline plugin. Also tested this in an app bundle and looked for instances of Platform.OS than should be inlined and made sure there was none.

@facebook-github-bot
Copy link
Contributor

Hi @IvanIhnatsiuk!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. labels Jun 22, 2025
@facebook-github-bot
Copy link
Contributor

@rshest has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants