Be more aggressive about minification

[danvk]

There are two things going on here:

• Using -g [ envify ] instead of -t [envify] applies the transform globally (i.e. including to code in node_modules), rather than just to our code. This means that it sets the NODE_ENV variable inside of React.
• The uglifyify transform minifies each module as browserify sees it. This means that dead require statements are removed.

These combine to shrink React pretty dramatically, since all the dev-mode code can be stripped.

452,690 pileup.min.js before
394,079 pileup.min.js after

∆ = 58,611 bytes (13%)

Looking at the source map, most of the difference is coming from React:

207,354 /react before (172 files in bundle)
139,935 /react after (167* files in bundle)

∆ = 67,419 bytes (33%)

Closes #307

* the dropped files are:

node_modules/react/lib/ReactDefaultPerf.js
node_modules/react/lib/ReactDefaultPerfAnalysis.js
node_modules/react/lib/ReactTestUtils.js
node_modules/react/lib/performance.js
node_modules/react/lib/performanceNow.js

[danvk]

cc @ihodes

[armish]

does this lead to double uglification (first via uglifyify and then directly via uglify)?

[danvk]

Yes -- though this is actually recommended!

When using uglifyify you should generally also use Uglify, to achieve the smallest output. Uglifyify provides an additional optimization when used with Uglify, but does not provide all of the optimization that using Uglify on its own does, so it's not a replacement.

[armish]

aha, magic 🔮

[armish]

File size looks remarkably small now! Thanks for testing these options out, @danvk.