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 🙏

© 2025 – Pkg Stats / Ryan Hefner

cache-hit

v2.0.0

Published

JavaScript promise caching library

Readme

cache-hit

JavaScript promise caching library

Types

options

|Option |Required|Description |Default value | |----------------|--------|----------------------------------------------------------------|-----------------------------| |timeToLive | No | An integer value that the cache is valid for in milliseconds |Number.POSITIVE_INFINITY |

Omitting timeToLive Option

This will result in an infinite cache. Once a successful response is received, the promise will never be invoked a second time.

Cache

interface Cache {
  read: () => Promise
}

API

createCache(promiseReturningFunction: () => Promise, options): Cache

PARAMETERS

promiseReturningFunction

A function that when called, will return a promise. The promiseReturningFunction is invoked from within the library.

options

Object of options. Supported options are listed in the Types section.

Return Value

Returns a Cache type.

Cache.read({ key: string, forceRead: Boolean }, ...promiseParameters: any): Promise

PARAMETERS

key

Data returned will be stored in the cache based on a key. Whenever reads occur, the cache will first be checked for a valid cache value and return the cached value or in the case of an invalid cache, the promise will be invoked and data will be stored in the cache depending on your timeToLive option.

forceRead

Defaulted to false. If this is set to true, the promise will be invoked regardless of the caching policy.

promiseParameters

Parameters that will be spread into the promiseReturningFunction. An example of calling this function exists below.

getAccountsApiCached.read({ key: 'some-key' }, param1, param2);

Example

// get-accounts.js
import createCache from 'cache-hit';

const getAccountsApi = (username, sessionId) => fetch(`/accounts/${username}`, { headers: { sessionId });

const getAccountsApiCached = createCache(getAccountsApi, { timeToLive: 15000 }); // timeToLive in milliseconds

export default getAccountsApiCached;
// accounts.js
import getAccountsApiCached from './get-accounts';

const getAccounts = (username, sessionId) => {
  const key = username; // unique key for this cache instance
  return getAccountsApi
          .read({ key: key, forceInvoke: false }, username, sessionId)
          .then((response) => dispatch(someAction(response)))
          .catch((error) => dispatch(someErrorAction(error)));
};

Errors

All errors will need to be handled after calling the read method. The cache will not be updated on any rejected promises.