Closed EvanBacon closed 1 year ago
@robhogan has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
Looks good to me, but there's a Flow error in packages/metro/src/commands/build.js
(aren't we running Flow in CircleCI? Maybe not on PRs?)
@robhogan has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
Maybe not on PRs?
We always used to, but this was turned off on CircleCI for PRs from forks, not sure when/why - I've just re-enabled it.
Lint error now is due to an internal callsite that needs updating - I'll take care of that.
@robhogan merged this pull request in facebook/metro@b2f43eee767b0a4ebd8ce7b84d489d3a9742e409.
Summary
We use
customTransformOptions
in Expo CLI to inform Metro that we're bundling for a Node.js environment (in addition to theplatform=web
), but the logger has no way of indicating to the user that a bundle is Server-specific. This change would enable us to refine the bundling message based on the additional criteria. We can do this if we skip over the server (exports/builds) but it'd be good to have parity. Example usage, corresponding output.Test plan