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

node-shared-structures

v1.0.8

Published

Implementation of a few basic thread-unsafe, constant-size data structures on top of SharedArrayBuffer for Node.js

Downloads

11

Readme

node-shared-structures

Implementation of a few basic data structures on top of SharedArrayBuffer for Node.js

The structures are not thread safe and are constant-size (although the latter is intended to change).

Currently implemented:

  • simple map (number => number)
  • linked list (number => number[])
  • variable size value array (number => Buffer)
  • hash map (string => Buffer)

The intended use case is when you have a bunch of simple, read-only data you want to share with Worker threads so that they don't have to have their own copies.

Performance of reading by key from the hashmap is basically O(1), i.e. doesn't depend on the size of the dataset.

Usage example:

const rows = 10;
const averageKeySize = 5; // bytes
const averageValueSize = 30; // bytes
const keyEncoding = "ascii";

const map = new SharedHashMap(rows, averageKeySize, averageValueSize, keyEncopding);

map.set("orange", Buffer.from("Oranges are pretty sweet."));
map.set("kiwi", Buffer.from  ("Kiwis should get a haircut."));

console.log(map.get("orange")); prints "Oranges are pretty sweet."
console.log(map.tryGet("banana")); // prints "undefined"
console.log(map.get("plum")); // Throws an exception