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

compact-encoding-maybe-enum

v1.0.2

Published

Generate compact encoding for defined enum or limited length arbitrary string

Downloads

96

Readme

compact-encoding-maybe-enum

Generate compact encoding for defined enum or limited length arbitrary string

why

An example of where this might be useful is encoding the value of a type property, where a set of strings are expected to be used 90% of the time, so encoding them as strings is quite wasteful, but you don't want to prohibit arbitrary strings either.

The trade-off used here is to:

  • limit the arbitrary string length to 127 character.
  • limit the enum to 128 member.

This way, we only need to store a value between 0 - 127 in the first byte, while the msb indicates whether the string is encoded as an enum or a string .

How it works

0000 0000 => 0111 1111 values encode the index of the enum member.

1000 0000 => 1111 1111 values encode the length of the arbitrary string, after switching the msb to 0 (xor 0x80).

Installation

npm install compact-encoding-maybe-enum

Usage

import c from 'compact-encoding';
import { maybeEnum } from 'compact-encoding-maybe-enum';

const enc = maybeEnum(['foo', 'bar']);

// Encoding decoding a member of enum
const encoded = c.encode(enc, 'bar');
//=> <Buffer 0x01>
const decoded = c.decode(enc, encoded);
//=> 'bar'

// Encoding decoding arbitrary string
const encoded = c.encode(enc, 'x');
//=> <Buffer 81 78>
const decoded = c.decode(enc, encoded);
//=> 'x'

API

const enc = maybeEnum(members)

members should be an array of unique strings (set) with maximum length of 0x80 (128) members.

with compact encoding: c.encode(enc, value)

value should be a string from members, or an arbitrary string with maximum length of 0x7f (127) characters.