deflateSync
anddeflate
- Compress raw string and encode in base64
- Node.js only
- The highest performance (Using native
zlib
) - Synchronous and Asynchronous
- The smallest size (minified)
0.13KB
/0.17KB
inflateSync
andinflate
- Decompress base64 string to raw string
- Browser only (Using
Uint8Array
andTextDecoder
) - Higher performance (Using tiny-inflate)
- Synchronous and Asynchronous/Multi-thread (Using Worker)
- Smaller size (minified)
3.16KB
/3.62KB
compress
/decompress
- Using lz-string compress/decompress in base64 only
- Both browser and Node.js
- Normal performance
- Synchronous only
- The smallest size (minified)
1.75KB
/1.67KB
createScriptLoader
- create script loader
npm install lz-utils
import {
compress, decompress,
deflateSync, deflate,
inflateSync, inflate
} from 'lz-utils';
const raw = "this is string";
const cs = compress(raw);
const ds = decompress(cs);
- The business here is to generate a lot of
html reports
to users or customers, so the report needs to be generated asfast
as possible and the file size should be assmall
as possible. - The possible process is to compress the report data and bundle it with the html file. When the user opens the html file in the browser, the report data will be
self-decompressed
and rendered in the browser. So that's whyinflate
browser only. - Why
base64
? First of all, the data is stored inJSON
format, which is easily serialized and compressed. At this time, we getbinary
data. Although its size is the smallest, it has many problems, such assecurity issues
(CORS) because it is not JS type or object, so we need to convert binary data into JS string, andbase64
is a good choice.
- string-compression lz-string, pako, uzip.js, fflate, tiny-inflate
-
2.1.0
- added
createScriptLoader
- added
-
2.0.2
- added types
-
2.0.0
- added tiny-inflate
-
1.0.7
- added ESM supported
-
1.0.5
- added browser version