/lz-string

Latest release
Fix for IE6&7
Latest release

@pieroxy pieroxy released this May 25, 2015 · 9 commits to master since this release

Assets 2

Removed the use of the bracket notation for accessing chars in a string.

amd loaders code and typescript support

@pieroxy pieroxy released this Apr 26, 2015 · 17 commits to master since this release

Assets 2 
1.4.3

Prepare version 1.4.3
Bugfix in decompressFromEncodedURIComponent

@pieroxy pieroxy released this Mar 25, 2015 · 29 commits to master since this release

Assets 2

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.

Uses arrays instead of strings when building the output

@pieroxy pieroxy released this Mar 23, 2015 · 31 commits to master since this release

Assets 2

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.

Rewrite of wrappers functions to use the compression method directly

@pieroxy pieroxy released this Feb 19, 2015 · 38 commits to master since this release

Assets 2

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.

The jsperf (Please take them to add more results and help me prove my theory):

http://jsperf.com/lzstring-1-3-8-vs-1-4-0-forcompress/2
http://jsperf.com/lzstring-1-3-8-vs-1-4-0-for-utf16
http://jsperf.com/lzstring-1-3-8-vs-1-4-0-for-base64
http://jsperf.com/lzstring-1-3-8-vs-1-4-0-for-uri-component

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.

Fix in decompressFromUint8Array

@pieroxy pieroxy released this Feb 18, 2015 · 43 commits to master since this release

Assets 2 
1.3.9

Prepare v1.3.9
Performance optimizations

@pieroxy pieroxy released this Feb 15, 2015 · 52 commits to master since this release

Assets 2 
1.3.8

Prepared v1.3.8
Updated bower.json file

@pieroxy pieroxy released this Jan 16, 2015 · 57 commits to master since this release

Assets 2 
1.3.7

Update lz-string.js
Bugfix on compressToEncodedURIComponent

@pieroxy pieroxy released this Jan 16, 2015 · 62 commits to master since this release

Assets 2 
1.3.6

Create bower.json
Ability to compress directly into a URI encoded string

@pieroxy pieroxy released this Nov 30, 2014 · 66 commits to master since this release

Assets 2 
Added two new methods:

compressToEncodedURIComponent: compress into a string that is already URI encoded

decompressFromEncodedURIComponent: the associated decompress method