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

@chat-adapter/state-redis

v4.20.1

Published

Redis state adapter for chat (production)

Readme

@chat-adapter/state-redis

npm version npm downloads

Production state adapter for Chat SDK using the official redis package.

Installation

pnpm add @chat-adapter/state-redis

Usage

createRedisState() auto-detects the REDIS_URL environment variable, so you can call it with no arguments:

import { Chat } from "chat";
import { createRedisState } from "@chat-adapter/state-redis";

const bot = new Chat({
  userName: "mybot",
  adapters: { /* ... */ },
  state: createRedisState(),
});

To provide a URL explicitly:

const state = createRedisState({ url: "redis://localhost:6379" });

Using an existing client

If you already have a connected Redis client, pass it directly:

import { createClient } from "redis";

const client = createClient({ url: "redis://localhost:6379" });
await client.connect();

const state = createRedisState({ client });

Key prefix

All keys are namespaced under a configurable prefix (default: "chat-sdk"):

const state = createRedisState({
  url: process.env.REDIS_URL!,
  keyPrefix: "my-bot",
});

Configuration

| Option | Required | Description | |--------|----------|-------------| | url | No* | Redis connection URL (auto-detected from REDIS_URL) | | client | No | Existing redis client instance | | keyPrefix | No | Prefix for all keys (default: "chat-sdk") | | logger | No | Logger instance (defaults to ConsoleLogger("info")) |

*Either url, REDIS_URL env var, or client is required.

Environment variables

REDIS_URL=redis://localhost:6379

For serverless deployments (Vercel, AWS Lambda), use a serverless-compatible Redis provider like Upstash.

Key structure

{keyPrefix}:subscriptions     - SET of subscribed thread IDs
{keyPrefix}:lock:{threadId}   - Lock key with TTL

Production recommendations

  • Use Redis 6.0+ for best performance
  • Enable Redis persistence (RDB or AOF)
  • Use Redis Cluster for high availability
  • Set appropriate memory limits

Features

| Feature | Supported | |---------|-----------| | Persistence | Yes | | Multi-instance | Yes | | Subscriptions | Yes | | Distributed locking | Yes | | Key-value caching | Yes | | Automatic reconnection | Yes | | Key prefix namespacing | Yes |

License

MIT