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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nphyx/vanderpool

v0.0.1

Published

A lightweight, low-level tool for managing pools of structured ArrayBuffer data.

Readme

VanderPool 0.1

VanderPool is a lightweight, low-level tool for managing pools of structured ArrayBuffer data.

Why?

Suppose you have a structured data type built on top of an ArrayBuffer (say a TypedArray or DataView). Your program needs tons of these, and it frequently creates and destroys them. You could use a regular ol' object pool containing thousands of little ArrayBuffers, but wouldn't it be better if the underlying data was one big ArrayBuffer instead?

VanderPool gives you the one big ArrayBuffer and a safe, reliable, fast way to manage it. You may want to build an object pool on top of that, but that's none of VanderPool's business. It just handles keeping track of what segments of the buffer are in use and which parts are ready to be reused.

Usage

// ES6 style
import VanderPool from "vanderpool/src";

// or commonJS style (the index.js in the project root is transpiled and webpacked)
let VanderPool = require("vanderpool").default;

// suppose we want a pool of 1000 items of 8 bytes each
const pool = new VanderPool(8, 1000);

// VanderPool's allocator accepts a callback in the form 
// function(buffer, byteOffset, byteLength)

// you can pass the params directly to a DataView constructor
let dv = pool.allocate((buf, bo, bl) => new DataView(buf, bo, bl));

// or to any arbitrary object you want to use
let myObj = pool.allocate(myObjFactory);

// once you're done with it, call free with the offset:
pool.free(dv.byteOffset);

// (don't forget to keep track of this if you're using a custom object during allocations)
// keep in mind that TypedArrays expect an item length, not a byte length
let f32arr = pool.allocate((buf, bo, bl) => new Float32Array(buf, bo, 2));

// Also keep in mind if you're using TypedArrays the byte length of VanderPool members
// must be even multiples of the typed array's BYTES_PER_ELEMENT 
let pool2 = new VanderPool(7, 1000);
// the first one will work...
let f32arr = pool.allocate((buf, bo, bl) => new Float32Array(buf, bo, 1));
// but the second one will crap out
let f32arr2 = pool.allocate((buf, bo, bl) => new Float32Array(buf, bo, 1)); // RangeError

License

MIT