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 🙏

© 2025 – Pkg Stats / Ryan Hefner

incremental-encoder

v0.0.1

Published

A small [incremental encoder][#wikipedia-incremental-encoding] in TypeScript.

Downloads

7,704

Readme

incremental-encoder

A small incremental encoder in TypeScript.

How it works

Read the wikipedia article first. I try to mirror the idea presented there by taking a list of words and creating a small encoded list by sharing common suffixes.

For example,

The list

word
world

This list consumes 11 bytes including the return character.

Encoded, this list looks like:

0wor
3ld

This encoded list consumes 8 bytes including the return character.

In the encoded list, the first character is a Base36 number indicating how many prefix characters are shared with the previous word. The rest of the line is the non-shared suffix of the word.

If there were a 3rd word in the list, its count of shared characters would be calculated against the 2nd word, the 4th against the 3rd and so on.

Usage

Encoding

import { Encoder } from 'incremental-encoder';

const wordList = ['word1', 'word2', 'word3', ...];

const encoder = new Encoder();
const encodedWordList = encoder.encode(wordList);

Decoding

import { Decoder } from 'incremental-encoder';

const decoder = new Decoder();
const wordList = decoder.decode(encodedWordList);
// wordList should be the same as in
// the Encoding example

Limitations

To maximize space savings, a strict encoded output format is used. The first character always represents the number of characters shared with the previous word. Because JavaScript's Number.prototype.toString only supports up to base 36, the maximum number of shared characters between words is 35.

License

MPL-2.0