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

vectrie

v1.0.0

Published

JS implementation of persistent bit-partitioned vector trie a.k.a vector data structure in Clojure

Downloads

3

Readme

vectrie

JS implementation of persistent bit-partitioned vector trie a.k.a vector data structure in Clojure.

Library provides PersistentVector immutable and fully persistent data type with O(log32 N) get and set operations, and O(1) push and pop operations.

In addition companion MutableVector mutabale dual is provided for performance critical code paths and batch operations that provides compatible API but with a smaller memory overhead.

Usage

import * as Vec from "vectrie"

const pv1 = Vec.from([1, 2, 3, 4])
Vec.get(pv1, 0) // => 1
Vec.get(pv1, 4) // => undefined
Vec.get(pv1, 4, "not-found") // => not-found

const pv2 = Vec.push(pv1, 5)
Vec.get(pv2, 4) // => 5

In performance critical code & batch operations you can use transient vector:

let tv = Vec.mutable.from(pv1)
for (const n of input) {
  tv = Vec.mutable.push(tv, n)
}
const pv3 = Vec.seal(tv)

If you want some sugar and more conventional JS API, there is PersistentVectorView to help you with that:

const v1 = Vec.PersistentVectorView.from([1, 2, 3, 4])
v1.get(0) // => 1
v1[0] // => 1

const v2 = v1.set(0, 5)
v2[0] // => 5

Comparison to alternatives

ImmutableJS

ImmutableJS is a good and a lot more mature library which comes with a lot more data structures out of the box. List data structure is an equivalent of a PersistentVector and to my knowledge they are both ports of the Clojure's vector implementation. Here is how this library differs

  1. vectrie (deliberately) provides only PersistentVector data type.

  2. vectrie is written in typescript (JS with JSDoc types to be accurate) which affects API design:

    • PersistentVector<T> unlike Immutable.List is continues and not sparse. It would be fare to say that PersistentVector<T> is more like Vector in rust while Immutable.List is more like JS Array.

    • Setting out of bound value on PersistentVector a RangeError while in Immutable.List it creates sparse list.

    • PersistentVector<T> has no splice, slice, unshift, reverse because there is no effecient way to perfrom those operations on bit-partitioned vector tries while retaining desired performance profile (which is why both clojure and immutable JS return different data structure when you do so).

      vectrie does not do that because in many cases modeling data with different types is a better alternative to abstracting it away.

  3. PersistentVector implementation decouples data from operations that can be performed on it. This makes moving them across realms / threads, serailzing / deserializing hassle free.

    Library also provides sugar via PersistentVectorView to provide more conventional API in JS. It also makes it possible for you to write your own View providing alternative API without inheritence or other counterproductive features.

  4. PersistentVectorView provides indexed access to underlying elements (e.g. pv[0] to get first element) which is of questionable benefit, but does seem more natural in JS. Note that updates do not work the same way.

Immer

Immer is popular library which provide immutablity from the comfort of the mutable interface. Vectrie library borrows from clojure transients and goes other way round, providing mutability (when needed) from the comfort of immutable interface.