Reduced build for raw deflate/inflate? about pako HOT 5 CLOSED

Personally I just use the lib folder in a git submodule and depend on my build tools to extract the files I actually need. Thanks for an awesome library that's so easy to consume.

My submodules for 3rd party code: https://github.com/creationix/tedit-app/tree/master/lib
My build rule that pulls in the lib folder: https://github.com/creationix/tedit-app/blob/master/chrome-app/src/pako.rule

from pako.

Yes, lib is specially designed to be requireable by separate files. I meaned another case - if someone need "pure raw deflate only", it's possible to additionally reduce size by cutting gzip support, strings conversion, deflate header wrapper, and some other deflate methods.

But, honestly, i think that's not significant in real life, and doesn't worth of spending time :)

from pako.

Considering this is already orders of magnitude smaller than the emscripten version of zlib, I'm happy with the size.

If you structured the code right, a really smart compressor could see which methods I use in the library and trim unused/dead code. I don't use string conversion or gzip support. I just need deflate/inflate as used in git.

But I agree that since size isn't an issue for me with pako, I don't worry about it.

I'm interested to hear what others think.

from pako.

• Stuk/jszip#102 (comment) JSZip devs agreed, that size difference is not so big to care about.
• browserify with 'zlib' support adds much more overhead with buffers/streams and other shims, so pako size cut is not significant there.

AFAIK, that's the most big projects, that requires pako.

from pako.

closed - timed out / not really needed

from pako.