Minifyify
Tiny, Debuggable Browserify Bundles
Before, browserify made you choose between sane debugging and sane load times. Now, you can have both.
Minifyify minifies your bundle and pulls the source map out into a separate file. Now you can deploy a minified bundle in production, and still have a sourcemap handy for when things inevitably break!
Usage
var browserify = require('browserify')
, minifyify = require('minifyify')
, path = require('path')
, bundle = new browserify()
, opts = {
file: '/bundle.js'
, map: '/bundle.map'
, transforms: {
hbsfy: require('hbsfy')
, envify: require('envify')
}
};
bundle.add('entryScript.js');
minifyify(bundle, opts, function(code, map) {
fs.writeFileSync('www/bundle.js', code);
fs.writeFileSync('www/bundle.map', map);
});
FAQ
-
How does this work?
Minifyify uses the --list
advanced option in browserify to discover what files are in your bundle. It then uglifies each file, adds an inline sourcemap, and runs browserify on the minified files. Browserify will combine and offset the sourcemaps.
-
Why don't I apply transforms myself?
Minifyify needs to know your transforms to create the dependency graph and minify things like precompiled templates. Since there is no public API to do this in browserify, transforms have to be specified as an option.
-
Why does the sourcemap cause my debugger to behave erratically?
Some of the optimizations UglifyJS performs will result in sourcemaps that appear to broken. For example, when UglifyJS uses the comma operator to shorten statements on different lines, a single debugger "step" in minified code may execute multiple lines of the original source.
License
MIT