Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve build #816

Merged
merged 2 commits into from
Jan 15, 2017
Merged

Improve build #816

merged 2 commits into from
Jan 15, 2017

Conversation

ericf
Copy link
Collaborator

@ericf ericf commented Jan 15, 2017

This upgrades to rollup@0.41.4 which fixes issues with ES3 Babel transforms and Babel helpers which has reduced the build file size.

File Before After Delta
react-intl.min.js 47.10 kb 41.61 kb -11.66%
react-intl.min.js.gz 13.31 kb 11.51 kb -13.52%

Fixes #814
Relates #788, #687

This upgrades to `rollup@0.41.4` which fixes issues with ES3 Babel
transforms and Babel helpers which has reduced the build file size.

File | Before | After | Delta
---- | ------ | ----- | -----
react-intl.min.js | 47.10 kb | 41.61 kb | -11.66%
react-intl.min.js.gz | 13.31 kb | 11.51 kb | -13.52%

Fixes formatjs#814
Relates formatjs#788, formatjs#687
@yahoocla
Copy link

CLA is valid!

@ericf ericf merged commit e3dc8bb into formatjs:master Jan 15, 2017
@ericf ericf deleted the improve-build branch January 15, 2017 00:33
indexzero added a commit to indexzero/react-intl that referenced this pull request Apr 20, 2017
We say "soft" breaking because it was not a strict contract between `react-intl` and
consumers that raw `src/*` files be included in the npm package. If one were to want
a custom build of `react-intl` for their own purposes the npm package is now no longer
a viable location for that source code.
okuryu pushed a commit that referenced this pull request Sep 1, 2017
We say "soft" breaking because it was not a strict contract between `react-intl` and
consumers that raw `src/*` files be included in the npm package. If one were to want
a custom build of `react-intl` for their own purposes the npm package is now no longer
a viable location for that source code.
@okuryu okuryu mentioned this pull request Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"await" error in Microsoft Edge
2 participants