Meteorites, we have published our 0.3.0 release of our minification plugin: ssrwpo:uglifyjs2. This release adds new options allowing to decrease even more your JS payload. You can find a demo in our repository as well as some documentation in our website: https://ssrwpo.github.io/uglifyjs2/
Unfortunately, we have the same problem as the standard-minifier-js as both rely on UglifyJS2.
I was thinking about using babili to avoid them but having Babel triggered twice from the ecmascript and the minifier package seems wrong to me. A single package that would do the transpiling and the minification would be far better.
At least, this package shaves off some of the Meteor.isSever as well as the process.env.NODE_ENV === 'production' that are left in the client. On React sites, it means a lot.
Apart that it lenghtens the production build a little bit, it’s definitely worth using it. I will add an issue for it. Having it in the core would be far more effective and would benefit our community even more.
I tried using this package but have given up after waiting for an hour and a build still had not completed.
I started to wonder if it might be because I have already minified files, maybe @sashko you could answer this for me. I know that you can use “.min.js” to tell Meteor to not minify files, and you can use “.es5.js” to tell Meteor to not run it though babel. Is there a way to have both?
I got it working after renaming my minified files to .min.js. It took quite a while to minify, but my project is fairly large. Unfortunately, for me it didn’t cut down on the size of the JS, 1.8 MB gzipped prior and 1.8 MB gzipped after.