Simple, tiny and fast ZIP library. It has our own DEFLATE compressor and decompressor (alternative to pako.js / ZLIB). It was made from scratch, without using existing implementations.
UZIP.js is faster than pako.js
Web: Add the UZIP.js
script to your webpage:
<script src="https://github.com/photopea/UZIP.js/raw/master/UZIP.js"></script>
NodeJS: Install the uzip
package:
npm install uzip
UZIP.parse(buff)
buff
: ArrayBuffer of the ZIP filekey : property
pairs, where key
is a file name (String), and property
is a file (Uint8Array)UZIP.encode(obj)
obj
: object with key : property
pairs (see above)Directories should be "included" inside file names.
var obj = { "file.txt":new Uint8Array([72,69,76,76,79]), "dir/photo.jpg":..., "dir/pic.png":... };
var zip = UZIP.encode(obj);
The API is the same as the API of pako.js, just use UZIP.xyz...
instead of pako.xyz...
.
UZIP.deflateRaw(buff)
buff
: Uint8Array of the original fileUZIP.deflate(buff)
buff
: Uint8Array of the original fileThese two functions have an optional third parameter: Options object,
which can be {level:L}
, where L is the level of compression (0 to 9).
UZIP.inflateRaw(buff)
buff
: Uint8Array containing the deflate streamUZIP.inflate(buff)
buff
: Uint8Array containing the ZLIB streamThese two functions have an optional third parameter: Output buffer (Uint8Array).
DEFLATE or ZLIB stream do not directly store the size of the output uncompressed data. Decompressors usually write the result into a small array, which is enlarged (copied into a bigger array) during the process.
Practical applications of DEFLATE (like ZIP or PNG files) usually store the size of uncompressed data. If you provide the output buffer, decompression is faster (no need for gradual enlarging of the output array).