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

@djs-commands/adapter-redis

v2.0.1

Published

Redis CacheAdapter for djs-commands cooldowns — distributed, TTL-native cooldown storage

Downloads

209

Readme

@djs-commands/adapter-redis

Redis-backed CacheAdapter for @djs-commands/core cooldowns.

Distributed, TTL-native cooldown storage so sharded bots have consistent cooldowns across processes. Uses SET key value PX <ms> for atomic set-with-TTL — Redis stores the absolute expiry timestamp as the value AND auto-evicts the key when the TTL elapses, so you never accumulate dead entries.

📘 Full walk-through: https://djscommands.deoxy.dev/adapter-cookbook#redis-cache-adapter-not-storage

Install

bun add @djs-commands/core @djs-commands/adapter-redis ioredis

ioredis and @djs-commands/core are peer dependencies — install them in your app.

Usage

Pass an ioredis instance (URL, config, sentinel, cluster — whatever you like) into redisCacheAdapter, then hand the returned adapter to your command handler via the cacheAdapter option.

import { Client, GatewayIntentBits } from "discord.js";
import { createCommandHandler } from "@djs-commands/core";
import { redisCacheAdapter } from "@djs-commands/adapter-redis";
import Redis from "ioredis";

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

const client = new Client({ intents: [GatewayIntentBits.Guilds] });

createCommandHandler({
  client,
  commands: [/* ... */],
  cacheAdapter: redisCacheAdapter(redis),
});

await client.login(process.env.DISCORD_TOKEN);

Pair this with one of the storage adapters (drizzle / prisma / mongoose) for full persistence — Storage covers prefixes/locks (durable, low-traffic), CacheAdapter covers cooldowns (hot path, ephemeral).

Multi-bot deployments: keyPrefix

When several bots share a single Redis instance, give each one a distinct prefix to avoid collisions:

const cacheAdapter = redisCacheAdapter(redis, { keyPrefix: "moderation-bot:" });

Every key the adapter reads or writes is prepended with this prefix. The default is "djs-commands:".

How it works

The adapter implements three methods from the CacheAdapter interface:

| Method | Redis command | | -------- | ------------------------------------------ | | set | SET <prefix><key> <expiresAt> PX <ttlMs> | | get | GET <prefix><key> then parse to number | | delete | DEL <prefix><key> |

get returns null for missing keys, non-numeric values, or timestamps in the past — defensive against clock skew.

Testing

Unit tests run with a mocked ioredis and don't require a Redis instance.

Integration tests run against a real Redis when REDIS_URL is set:

REDIS_URL=redis://localhost:6379 bun test

If REDIS_URL isn't set, the integration suite skips cleanly. Spin one up locally with:

docker run --rm -p 6379:6379 redis:7-alpine

License

MIT · Issues + discussions on GitHub.