Bundle size reduction

[matthargett]

Summary

With recent activity to extract out non-core things into separate repos, I did an audit of the package.json to see what can be removed, and what packages remain that have newer versions that result in less/smaller javascript code. The goal is to:

1. make developer experience better by removing unneeded dependencies, and
2. eliminate things the app bundler needs to process to make the production app bundle smaller.

Changelog

[internal] [chore] - Remove unneeded packages, bump package versions who now have smaller size

Test Plan

1. yarn lint
2. yarn flow
3. yarn test
4. yarn test-android-unit

[pull-bot]

	Warnings
⚠️	🔒 package.json - Changes were made to package.json. This will require a manual import by a Facebook employee.

Messages

📖

📋 Changelog Format - Did you include a Changelog? A changelog entry has the following format: [CATEGORY] [TYPE] - Message. CATEGORY may be: General iOS Android TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 073f03b

[sunnylqm]

And since jsc has been upgraded, maybe we can also remove some polyfill and babel plugins?

[cpojer]

Could you revert the changes to yargs and jest-junit for now?

How does this PR affect bundle size?

[matthargett]

And since jsc has been upgraded, maybe we can also remove some polyfill and babel plugins?

I'd love to do that, but I think there are some Facebook dependencies that need to be fixed first. Ideally, we could have a CLI flag that doesn't include the polyfills so OSS users aren't being held back by Facebook's deployment constraint. It's not just the bundle size, but the global initialization code that needs to run as well.

[matthargett]

Could you revert the changes to yargs and jest-junit for now?

Sure. Can you give some detail on the yargs constraint? That's probably the biggest savings in terms of bundle size (~13kb). Even updating it to 10.x (if somehow 13 is not workable for FB) would help.

How does this PR affect bundle size?

It's saving ~30kb when using haul in one of my apps. I can't seem to get consistent results when trying to compare using RNTester. There's this weird 80-100 byte variance I can't track down.

[cpojer]

Thanks!

[facebook-github-bot]

@cpojer is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[react-native-bot]

This pull request was successfully merged by @matthargett in 13351e6.

^{When will my fix make it into a release? | Upcoming Releases}