Those numbers are amazing 😄.

Trimming down is tricky, as each of Intl.complete.js, json and jsonp offer an alternative option based on the polyfill consumer's preference. Intl.complete.js is commonly only used in Node or packaged apps that run locally, whereas json and jsonp are lightweight alternatives for browser environments.

We could possibly ditch either jsonp (~20M, whitespace/key quotes stripped) or json (~56M, human readable), depending on which is more popular to serve. @caridy, what do you think?

I will work on this on Thursday.

ok, finally I get a chance to look at this problem holistically, here are my thoughts:

• FT polyfill service relies on the npm pkg to build their own folder structure (they use dist/ and locale-data/jsonp)
• People using browserify/webpack can choose individual locale data files (otherwise their bundle is unusable), and they do so from NPM :/, we can't really remove jsonp files from the pkg at this point.
• I suspect that others might use locale-data/json, and removing it from the pkg will require a version bump (but I think it is worth it, those account for more than a half of the pkg)
• I have revisited the docs, and the issues, and we've never talk about locale-data/json/, we might be fine.
• we can trimming everything else.

I will submit a PR soon.

https://github.com/andyearnshaw/Intl.js/releases/tag/v1.2.5

@bensontrent I did some partial clean up, but unfortunately we can't really remove dist/ because people are using it directly. I plan to do so in 1.3.x, in the meantime, I will keep this open.

@caridy An 80% reduction in the npm package size? That's more than a modest partial cleanup, I'd say that's a win already. Here's what intl looks like after your revisions:

And here's a report by file type report:

Nice work!

Glad to see the file size going down! But the json folder was removed in v1.2.5 -- for future reference, this should have probably been a major release, not a patch release, to avoid breaking the package for those of us that depended on it.

ok, with 1.2.6 we are going down to ~500K package (~5mb expanded), which I think is sufficient for now.

@bensontrent thanks a lot for pushing us to get to that point.

Holy cow @caridy I'm impressed - a 93% savings. And look how popular Intl has become since we first started this conversation in July--the stats have doubled on what was already a very popular package.

My (certainly-inaccurate) napkin calculation estimates the 93% reduction in size saves 60 Terabytes of storage and transmission, every day.

Way to go! 😃