[PROPOSAL] Build tool to optimise Imager library (so it includes only code actually used) about imager.js HOT 6 OPEN

Regarding #25 and some other, that's true it can become counter productive only for the sake of the filesize and the context. I like your idea of having some features shipped in the core experience and enabling them to build their own flavour by removing/adding other features at build time.

Additionally to a grunt task, it would make sense in combination with an updated @kaelig's Imager.js customiser.

from imager.js.

@oncletom sounds good to me

from imager.js.

Although a more complex example, you might find it useful looking at how grunt-modernizr solved this problem for their task for building leaner versions of Modernizr https://github.com/Modernizr/grunt-modernizr/tree/master/lib.

Alternatively, ensuring that all non-core features are shipped as plugins makes that task of dropping unused features at build-time a great deal more easy. This is the approach taken by the jQuery project and others who found actual build-time parsing to be a less ideal option.

from imager.js.

What do you think of browserify? If we use it to generate UMD module, we can use require() to load internal modules and create various bundle files. And it let people building their own flavour of Imager.

from imager.js.

For folks who like to keep everything in the same package manager, it's certainly a means to an end :)

On UMD: I think that as long as the final version built for the user doesn't suffer from too much wrapper overhead, that option is appealing and as you mention, would let us create various bundles.

from imager.js.

Agreed with @addyosmani on trying to prevent wrapper'itus if possible :-)

from imager.js.