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

@loke/cache-kit

v1.0.3

Published

## Examples

Downloads

768

Readme

LOKE cache-kit

Examples

Basic usage

For the most common cases use a simple 2 layer LRU + Redis cache is sufficient.

import { Cache, LruMemoryCacheStore, RedisCacheStore } from "@loke/cache-kit";
import Redis from "ioredis";
import { create as createLogger } from "@loke/logger";

const logger = createLogger();
const redisClient = new Redis();

const cache = new Cache(
  // Keys should be prefixed with the project name to make them unique across
  // all of LOKE
  "foo-service:users:fetch:{userId}",
  // Cache stores will be checked in order, and the first cache to return a
  // value will be used
  [new LruMemoryCacheStore({ max: 1000 }), new RedisCacheStore(redisClient)],
  logger,
);

const userId = 123;

const user = cache.apply({ userId }, async () => {
  // This function will only be called if the cache is empty
  const value = await fetch(`http://example.com/user/${userId}`);

  // the ttl is returned as part of the result so it can vary per request
  return {
    value,
    ttl: 60 * 60 * 1000, // 1 hour in milliseconds
  };
});

Single flight cache

In cases where you don't want the overhead of storing the value in a cache, you can use the cache for single flighting requests. Concurrent requests will piggyback on the result of the first request.

import { Cache } from "@loke/cache-kit";
import { create as createLogger } from "@loke/logger";

const logger = createLogger();

const cache = new Cache(
  "users:{userId}",
  // An empty list of caches will result in a single flight only cache, where
  // the value is only cached for the duration of the request
  [],
  logger,
);

TODO

  • [ ] JSON reviver support