Heavy package

I just noticed that pako’s npm package is rather heavy at 1.5MB: https://packagephobia.com/result?p=pako@2.0.3

Even though pako itself is not necessarily that big, it’s repeated many times: https://www.unpkg.com/browse/pako@2.0.3/dist/

Can some files be avoided? For example you could keep:

• minified file in browser
• minified ES5 file
• inflate for node
• deflate for node
• pako.js for node, that requires both inflate and deflate
• pako.js ESM (threeshakeable)

The current situation only benefits CDN users for browsers, but isn’t ideal for everyone else. The problem is that the more unique entry points you offer, the more likely is that sub-dependencies won’t be deduplicated, because one might require inflate.js and the next pako.min.js

Ideally, only this should be part of an npm package:

• inflate for node
• deflate for node
• pako.js for node, that requires both inflate and deflate
• pako.js ESM (threeshakeable)

[fregante]

• useless waste of time

To you maybe. Lambda has size limits, so they do matter.

• .tgz file size is 400K, not 1500K.

And adm-zip is 26K. Even jszip.tgz, which includes a 2 version, is 100K.

I think you understand why one would pick a more efficient package if it works the same in a scenario.

[ricardomozartlino]

I have the same problem, half the package size comes from this lib, very sad