lz-string
Advanced tools
Changelog
[1.4.4] - 2015-05-25
- Fix for IE6&7
- Removed the use of the bracket notation for accessing chars in a string.
Changelog
[1.4.2] - 2015-03-25
- Bugfix in decompressFromEncodedURIComponent
- On the server side, '+' characters are replaced by ' ' (whitespace) and the resulting string cannot be decompressed.
- The fix is ugly but it works and is 100% compatible with old versions.
Changelog
[1.4.1] - 2015-03-23
- Uses arrays instead of strings when building the output
- This ends up being slightly slower on some combinations of OS/Browser, but the process consumes far less memory, and the strings produced as well consumes much less memory.
Changelog
[1.4.0-beta] - 2015-02-19
This avoids calling compress and then re-encoding the results in UTF-16, base64 or URIEncoded string.
As a result:
- The compress method is slightly slower.
- The compressToUTF16, compressToBase64 and compressToEncodedURIComponent are slightly faster (in theory).
- Binary compatibility for decompression is still there. This means any String compressed with an old version of the library can be decompressed by this version, and any String compressed by version 1.4.0 can be decompressed by an older version.
- Binary compatibility for compression is not guaranteed, meaning the output from this version may be different than the output produced by an older version. This is trailing characters that are useless that are now omitted.
NOTE: Releasing this as the performaces seems good except for base64 and uri component on IE. Those don(t take too big of a hit and are designed to send the compressed data to the network (usually internet which is orders of magnitude slower than the compression algo). So I'm going with it.
Changelog
[1.3.6] - 2014-12-18
- Bugfix on compressToEncodedURIComponent and decompressFromEncodedURIComponent.
Changelog
[1.3.5] - 2014-11-30
- It allows compression to produce URI safe strings (ie: no need to URL encode them) through the method compressToEncodedURIComponent.