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-kit/cache-redis

v0.1.1

Published

Redis/Valkey CacheProvider for @cache-kit/cache, built against a structural client interface (works with ioredis, node-redis, or any compatible client).

Readme

@cache-kit/cache-redis

Redis/Valkey CacheProvider for @cache-kit/cache, built against a small structural client interface — works with ioredis, node-redis, or any compatible client. No hard dependency on either.

npm install @cache-kit/cache @cache-kit/cache-redis

With the ioredis reference adapter

ioredis is an optional peer dependency — only needed if you use this adapter. Importing the main package never requires it.

npm install ioredis
import Redis from 'ioredis';
import { Cache } from '@cache-kit/cache';
import { RedisProvider } from '@cache-kit/cache-redis';
import { createIoredisAdapter } from '@cache-kit/cache-redis/ioredis';

const redis = new Redis(process.env.REDIS_URL!);

const cache = new Cache({
  provider: new RedisProvider({
    type: 'redis', // use 'valkey' if you're on a Valkey server — same protocol, label only
    client: createIoredisAdapter(redis),
    keyPrefix: 'myapp',
  }),
});

Bring your own client instead by implementing RedisLikeClient (exported from this package) — a handful of methods (get, set, setex, del, sadd, smembers, mget, ...).

Cross-instance correctness

Tag and namespace invalidation (cache.invalidateTag(), cache.invalidateNamespace()) work correctly across multiple app instances sharing one Redis — not just within a single process. Every set() records tag/namespace membership into Redis Sets, and this provider implements search() so Cache can consult Redis directly rather than relying only on its local in-process index. See the doc comment at the top of redis-provider.ts for the full mechanism and its one known long-term consideration (stale Set membership after natural TTL expiry).

Known limitations, by design:

  • cache.clear() (whole-cache wipe, no namespace) throws — a shared Redis instance may hold other apps' keys; use cache.invalidateNamespace(), or flush at the Redis client level yourself if you really mean "everything".
  • cache.search() against a Redis-backed cache supports tags and namespace filters only; prefix/owner/source filters remain local-indexer-only (single-instance-correct).

License

MIT