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

@alexaegis/avl

v1.6.3

Published

Flexible AVL Tree for TypeScript

Downloads

149

Readme

AVL Tree

Build Status npm (scoped) Codacy Badge Maintainability Test Coverage Known Vulnerabilities code style: prettier Greenkeeper badge

Flexible AVL Tree for TypeScript and JavaScript

Install with NPM

npm i @alexaegis/avl

Import and Create

import { Tree } from '@alexaegis/avl';

const tree = new Tree<Key, Value>(); // Create
tree.set(key, value); // Set
const result: Value = tree.get(key) // Get

Usage

Although the typing does not enforce the key to have a compareTo method (to allow using any type of object as keys, not just what you created and have control over) The tree will throw runtime errors if it can't order the keys.

The most basic case is that the key is a string or a number, then the value itself can be directly converted to a string or a number (Implicit or explicit, either having a convertTo(): K method on the objects prototyle or supply a converter function to the Tree object), and then if the key is an object it has to be comparable (Implicit or explicit, either having a comparable(a: K, b: K): number method on the objects prototype or supply a converter function to the Tree object)

These functions you supply will al have their this value bound to the object the are getting applied on. For this reason if you want to use this in you comparator and/or converter methods use regular functions instead of lambdas.

Implicit keys - Comparable, Comparator

if the object you are using as a key contains a compareTo(T) method then it will work just fine

class Key {
	constructor(public key: number) {}
}
const tree = new Tree<Key, Value>();
tree.set(new Key(2), new Value(4)); // Cannot compare error

Using a Comparable

class Key implements Comparable<Key> {
	constructor(public key: number) {}
	compareTo(other: Key): number {
		return this.key - other.key;
	}
}
const tree = new Tree<Key, Value>();
tree.set(new Key(2), new Value(4)); // 👌 the key will be valid

Using a Comparator

Very important, if using a lambda as a comparator you cant use the this keyword in it (as usual), and the only type of comparator you can write is the 'two argumen' one as seen below. But you can use this if you use a regular anonym function. This will act the same as the one you would write while implementing the interface. There is an optional second argument here too, that's gonna be the same as a. But you don't need to use it.

class Key {
	constructor(public key: number) {}
}

let tree = new Tree<Key, Value>((a: Key, b: Key) => a.key - b.key); // Using Lambdas
// Because of the fancy inner binding, you can even write this. It's basically the same
tree = new Tree<Key, Value>(function (b: Key) { return this.key - b.key; });

tree.set(new Key(2), new Value(4)); // 👌 the key will be valid

Explicit keys - Convertable, Converter

Using a Convertable

Only using Converters/Convertables allows the usage of the push method! You can even convert to a comparable!

const tree = new Tree<Value>();
tree.push(new Value(4)); // Cannot convert error
export class Value implements Convertable {
    constructor(public n: number) {}
	convertTo(): number | string {
		return this.n;
	}
}

const tree = new Tree<Value>();
tree.push(new Value(4)); // 👌 the key will be 4

Using a Converter

Alternatively you can supply a function to act as the converter

export class Value {
    constructor(public n: number) {}
}
export class AnotherValue {
    constructor(public n: number) {}
}

const tree = new Tree<number, Value>(undefined, (val: Value) => val.n);
tree.push(new Value(4));
tree.push(new AnotherValue(1)); // You can do messy things like this without implementing a single interface

Using a Convertable that converts to a Comparable

This is great when you have a bunch of objects you want to quickly access by keys that are encapsulated within the object.

export class Coord implements Comparable<Coord> {
	constructor(public x: number = 0, public y: number = 0) {}
	compareTo(other: Coord): number {
		return this.y === other.y ? this.x - other.x : this.y - other.y;
	}
}

export class BasicConvertableToComparable implements Convertable<Coord> {
	constructor(private coord: Coord) {}
	convertTo(): Coord {
		return this.coord;
	}
}

const tree: Tree<Coord, BasicConvertableToComparable>;
tree.push(new BasicConvertableToComparable(new Coord(1, 1)));
tree.get(new Coord(1, 1)); // The BasicConvertableToComparable object you pushed in

Searching nearest values for missing keys

You can search for either nearest on left and nearest on right values if the one you search for might be missing.

const tree = new Tree<number, number>();
tree.set(1, 1);
tree.set(2, 2);
tree.set(4, 4);
tree.set(8, 8);
tree.set(7, 7);
tree.set(10, 10);
tree.set(14, 14);
tree.set(12, 12);

const last = tree.lastBefore(13.66); // 12
const first = tree.firstFrom(13.66); // 14
const enclosing = tree.enclosing(13.66); // {last: 12, first: 14}

// When you might need the keys too
const lastNode = tree.lastNodeBefore(13.66); // Node {h: 1, k: 12, v: 12}
const firstNode = tree.firstNodeFrom(13.66); // Node {h: 2, k: 14, v: 14, …}
const enclosingNodes = tree.enclosingNodes(13.66); // Object {last: Node {h: 1, k: 12, v: 12}, first: Node {h: 2, k: 14, v: 14, …}}

For more examples check the mocha tests


Technologies

Node 10

JavaScript runtime

NPM

Package manager for Node

TypeScript

Typed superset of JavaScript

TSLint

Linting tool

Mocha

Behaviour driven testing framework

Chai

Assertion library

Istanbul

Code coverage tool

Recommendations

Visual Studio Code

IDE for everything. Settings

Fira Code

Font with ligatures

Services

Travis CI

Continuous Integration solution

Codacy

Code Quality monitoring

Code Climate

Maintainability and Coverage reports

Snyk

Vulnerability detection

Shields.io

Badges to look cool