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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cley_faye/lzw

v2.0.0

Published

Pure JavaScript implementation of LZW compression

Downloads

448

Readme

@cley_faye/lzw

Pure JavaScript implementation of LZW compression

Provide a low-level implementation of the LZW algorithm as well as minimal support for compression/decompression of byte buffers.

Installation

npm install @cley_faye/lzw

Usage

The package uses the JavaScript ES module syntax.

Low-level usage

At low-level, LZW only handle numeric "codes" for both input and output. It is possible to create an instance able to compress any input dictionary, but for convenience functions to create a "byte" dictionary (handling all 256 values) is provided.

How to compress and decompress a sequence of input codes:

import {CodeCompress, CodeDecompress} from "@cley_faye/lzw";

const input = [1, 2, 3, 4];
// Compression
const compress = CodeCompress.createSingleBytes();
const compressed = [];
input.forEach(inputCode => {
  const outputCodes = compress.addInput(inputCode);
  if (outputCodes) {
    compressed.push(...outputCodes);
  }
});
const finalCodes = compress.endInput();
if (finalCodes) {
  compressed.push(...finalCodes);
}
console.log(compressed);
// Decompression
const decompress = CodeDecompress.createSingleBytes();
const decompressed = [];
compressed.forEach(inputCode => {
  const outputCodes = decompress.addInput(inputCode);
  decompressed.push(...outputCodes);
});
console.log(decompressed);

Usage with Uint8Array

Encoding of output codes into sequence of bits/bytes is also included.

Here's a basic example:

import {CompressBuf8, DecompressBuf8} from "@cley_faye/lzw";

const input = new Uint8Array([1, 2, 3, 4]);
// Compression
const compressed = CompressBuf8.compressBytes(input);
// Decompression
const decompressed = DecompressBuf8.decompressBytes(compressed);

You can also process chunks by creating an instance of CompressBuf8 or DecompressBuf8.

Encoding

This is incompatible with streams made with the version 1 of this library. Compressed Uint8Array are prefixed with a single byte indicating the settings from the compressor. Beyond that first byte, dictionary codes are output using the least amount of bit necessary to represent the largest entry of the dictionary. If configured, a reset code (256) and a stop code (257, or 256 if no reset code) are added to the dictionary on start/reset. The initial 256 first values of the dictionary are just their corresponding byte.

Settings

The library exposes most settings expected when handling LZW. Most notably:

  • Setting a limit to the dictionary size can be done using the maxCodeValue argument, either when creating a custom dictionary or with helper functions.
  • Outputing a "stop" code can be disabled with the setStop argument
  • Storage order (most significant bit first or not) is handled with the msb argument.

It is advised to leave the default values for setStop (true) and msb (true). Specifying a value for maxCodeValue will lower compression efficiency, but also limit the memory needed to compress/decompress, as the dictionary can grow quite large quite fast.