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

expiring-cache

v2.0.1

Published

An expiring in-memory cache!

Downloads

34

Readme

#expiring-cache

An expiring cache!

This is an in-memory cache which stores key/value pairs in a collection and invalidates them after a certain period of time. Useful for things that aren't really important enough to stick into a db, want to be kept around, and should not be kept around for the entire lifetime of the app.

The expiring-cache defines a particular fetch method which all keys must use, though the key is passed in such that you could make an API call based on the key, etc.

In addition, it requires all items in the cache to have the same maximum lifespan (though of course they expire at different times if they were inserted at different times). If each item in the cache needs its own expiry time, check out expiring-per-item-cache

Usage (typescript):

import ExpiringCache from 'expiring-cache';

const pause = (ms) => new Promise(resolve => setTimeout(resolve, ms));

async function getSomeNumberValueAsync(key: string) {
    let sum = 0;
    for (let i = 0; i < key.length; ++i) {
        sum += key.charCodeAt(i);
        await pause(Math.random() * 50);
    }
    
    return sum;
}

const expiringCache: ExpiringCache<string, number> = new ExpiringCache<string, number>({
    fetch: (key: string) => getSomeNumberValueAsync(key),
    expireTime: 5*60*1000, // 5 minutes
    clearTime: 2*60*1000 // 2 minutes 
});

async function main() {
    // As expected, if fetch's promise fails then this will also throw
    // Otherwise value is now a number.
    const value = await expiringCache.get('duck');
}

Upgrading from v1 to v2

  • Stop using Collection methods. They are not supported. If you reallllly need them, use the private _data property
  • (Optional, but recommended) switch to get and has from getValue and hasValid. They are aliases and identical.
  • If you use the expireTime property, it is now a Duration. Use expireTime.inMilliseconds instead.