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

redblack.js

v0.1.0

Published

A red-black tree for storage and retrieval of key/value pairs

Downloads

12

Readme

redblack

A red-black tree that supports value lookups by nearest key.

Acknowledgement

This implementation is based on (Julienne Walker's C Red Black Tree Tutorial)[http://eternallyconfuzzled.com/tuts/datastructures/jsw_tut_rbtree.aspx]. Huge thanks to her for sharing a detailed explanation and implementation of a pretty complex algorithm.

Use

	var rb = require( 'redblack' );
	var tree = rb();

The function to create a tree can take a custom comparator, but the default works fine for numbers and strings which are the only things you should be using for keys in this lib anyway.

API

add( key, value )

Adds the key value pair to the tree.

	tree.add( 'one', 1 );

count()

Returns the total number of key/value pairs stored in the tree.

	tree.count();

getValue( key )

Returns a value for the key if it exists.

	tree.getValue( 'one' ); // returns 1
	tree.getValue( 'missing' ); //returns undefined

nearest( key )

Returns either the value for the key or the value for the highest key less than the key provided.

	tree.nearest( 'two' ); // returns 1
	tree.add( 'six', 6 );
	tree.nearest( 'seven' ); // returns 1
	tree.nearest( 'yolo' ); // returns 6

remove( key )

Removes they key and corresponding value if found.

	tree.remove( 'six' );

Why another red black tree?

This lib really just exists to support a consistent hashing lib I wrote that uses a red black tree to keep nearest lookups O(log n). To do that, leaves needed to store a value in addition to the key to avoid having to perform an additional hash lookup once the nearest key is found.

If you're familiar w/ hash rings, this is probably a good enough explanation for why existing/traditional tree structures that only work with a key don't fit this use case.