Skip to content

Fix: platform inline transformation#1521

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

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

Conversation

@IvanIhnatsiuk

Copy link
Copy Markdown

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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
Contributor

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

@IvanIhnatsiuk

Copy link
Copy Markdown
Author

@robhogan Sorry for the tag, but I do not know who can I tag to ask about this PR 😄

Do you have any plans to merge/close this one?

@robhogan

robhogan commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

Hi @IvanIhnatsiuk - sorry this got dropped, I think #1641 might've superseded it? That was released in 0.83.4

@retyui

retyui commented Apr 19, 2026

Copy link
Copy Markdown
Contributor

@robhogan I've checked it on the latest ver. of react native (0.84.1)

and issue is still exist react/react-native#56344 (comment)

yarn why metro-transform-plugins                                             
├─ metro-transform-worker@npm:0.83.5
│  └─ metro-transform-plugins@npm:0.83.5 (via npm:0.83.5)
│
└─ metro@npm:0.83.5
   └─ metro-transform-plugins@npm:0.83.5 (via npm:0.83.5)

Can you merge this PR?

@robhogan

robhogan commented Apr 19, 2026

Copy link
Copy Markdown
Contributor

Can you merge this PR?

@retyui Not as is I'm afraid - it conflicts almost entirely with #1641.

This now needs a closer look to work out why #1641 didn't work as intended, and fix the current implementation.

@retyui

retyui commented Apr 20, 2026

Copy link
Copy Markdown
Contributor

@robhogan I debug current impl. and found the root cause

In general inline-plugin works if we import Platform from react-native


but some modules in react-native codebase use relative imports for Platform, for example:

import Platform from '../../Utilities/Platform'; // <- inline-plugin won't work

so inline plugin checks isPlatformNode returns false as
this relative imports isn't treated as imported from react-native package


As workaround we can use require, works well:

// 1. source code
const Platform = require('../../Utilities/Platform').default;
export const test = Platform.OS === 'ios' ? 'ios' : 'not-ios';

// 2. code before inline plugin
var Platform = require('../../Utilities/Platform').default;
var test = exports.test = Platform.OS === 'ios' ? 'ios' : 'not-ios';


// isPlatformNode 
//  -> isPlatformOS() 
//       -> isToplevelBinding() // <- true

// this line: https://github.com/thymikee/metro/blob/2fa8a8819d6c88b72fbb414d5c324df29546373e/packages/metro-transform-plugins/src/utils/createInlinePlatformChecks.js#L149

Code examples for tests:

// 1. source code
import Platform from '../../Utilities/Platform';
export const test = Platform.OS === 'ios' ? 'ios' : 'not-ios';

// 2. code before inline plugin
var _Platform = _interopRequireDefault(require("../../Utilities/Platform"));
var test = exports.test = _Platform.default.OS === 'ios' ? 'ios' : 'not-ios';

// ^^^ inline-plugin doesn't work 

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.

4 participants