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

cache-istos

v1.0.6

Published

very simple cache

Readme

cache clean

A cache style, very simple cache

The cache works in way similar to Unix page-stealer. A single asynchronous task wakes up at regular interval (the ttl in s.) and for each object referenced in the cache, performs one of the following :

  • if the reference is "marked" : remove it (steal it)
  • if the reference is not "marked" : mark it (preapare to steal)

The cache is used as a key/value map. Each time a reference is accessed by the application it is "unmarked", allowing it to stay in the cache at least on more cycle. A reference that is not accessed any more will remain in the cache between ttl and 2 * ttl seconds.

Install

npm i @habibouldmoussa/cache_istos

Usage

The following create a stealer task that will automatically stop when the application ends :

const stealer = new Stealer({ ttl: 2, unref: true });

By default, the stealer task won't stop automatically, this must be done by the application :

const stealer = new Stealer({ ttl: 2 });
...
stealer.destroy();

To set / get a reference to the stealer :

stealer.set("ref", {...});
...
const myRef = stealer.get("ref");

A reference can be deleted before it is stealed :

stealer.delete("ref");