npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lz-string-unsafe

v1.4.4-fork-1

Published

LZ-based (unsafe) compression algorithm

Downloads

106

Readme

lz-string-unsafe

LZ-based (unsafe) compression algorithm for JavaScript

Forked version

This fork is copied directly from https://github.com/JobLeonard/lz-string/tree/array-lookup branch.

We slapped a -fork-{local change index} suffix on the last version and pushed it to npm. The {local change index} is incremented whenever we make a change to the fork.

Why? Because we needed to include this library in our Stylus extension and every library we use needs to have a proper source location with a release (that isn't a beta version).

Install via npm

$ npm install -g lz-string-unsafe
$ lz-string-unsafe input.js > output.txt

Development

The lz-string-unsafe.js file in the root directory was modified independently of the source files located in the libs folder.

To create the lz-string-unsafe.min.js file, use the following in the command line:

$ npm run minify

This uses uglify-es to compress & create the minified file.

Open the tests/SpecRunner-unsafe.html file in the browser to test the minified file, since this is the version we're using in Stylus.

Home page

Home page for this program with examples, documentation and a live demo: http://pieroxy.net/blog/pages/lz-string/index.html