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

mpool

v0.2.0

Published

Micro object pooling library

Downloads

15

Readme

mpool

This library provides a simple object pool implementation.

Usage

import { Pool } from "mpool";

const pool = new Pool(() => ({ value: 0 }));

const obj = pool.get();
use(obj);
pool.put(obj);

The pool is unbounded, meaning that the pool never discards objects. To mitigate unbounded memory growth scenarios, the pool contains a .fit() method which shrinks the pool to pool.preferredSize objects, if there are more than pool.preferredSize objects in the pool. You may call this at the end of your game loop.

import { Pool } from "mpool";

class Thing {}

const pool = new Pool(() => new Thing, /* preferred pool size */ 5);
console.log(pool.length); // 5
pool.put(new Thing);
console.log(pool.length); // 6
pool.fit();
console.log(pool.length); // 5 <- pool has shrunk to our preferred pool size

The recommended way to handle initialization + deinitialization of your objects is to implement init and free, for example:

import { Pool } from "mpool";

class Thing {
    public value!: number;

    init(value: number): this {
        this.value = value;
        return this;
    }

    free() {
        // be careful: since `init` is *not* called automatically, `this.value` may be undefined.
        // in your own code, you should provide default values and employ null checks to mitigate this.
        console.log(`freed object: Thing { value: ${this.value} }`);
        return this;
    }
}

const pool = new Pool(
    // callback used for creating new objects when there aren't any in the pool
    () => new Thing,
    // callback used for freeing objects when they are discarded after
    // a call to `.fit()`
    o => o.free(),
    // preferred size of the pool, calling `.fit()` will only leave at most
    // this many objects in the pool
    0
);
// When acquiring an object, explicitly initialize it:
const obj = pool.get().init(100);
use(obj);
// at this point you may `.free()` your object, or return it to the pool
pool.put(obj);
// if at some point you `.fit()` the pool, the `free` callback will be called with
// every object beyond capacity, and those objects will be discarded
pool.fit(); // logs 'freed object: Thing { value: 100 }'