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

@healthzkit/redis

v0.0.7

Published

Redis health-check adapters for healthzkit (ioredis, node-redis, and Upstash).

Readme

@healthzkit/redis

Redis health adapters for healthzkit. Each adapter implements HealthAdapter by running a lightweight command (default PING) and returning latency in metadata.

Install the Redis client you use as a peer dependency; only that adapter’s subpath needs to be imported.

Install

npm install healthzkit @healthzkit/redis

Pick one client (peer dependency):

npm install ioredis          # for @healthzkit/redis/ioredis
npm install redis            # for @healthzkit/redis/redis
npm install @upstash/redis   # for @healthzkit/redis/upstash

The package is ESM-only ("type": "module").

Quick start

import { createHealthKit } from "healthzkit";
import { ioredisAdapter } from "@healthzkit/redis/ioredis";

const kit = createHealthKit({
  checks: [
    {
      name: "redis",
      type: ["readiness"],
      adapter: ioredisAdapter({
        connectionString: process.env.REDIS_URL!,
      }),
    },
  ],
});

Use a subpath import so unused clients are not pulled in:

| Client | Import | Adapter | | ---------------------------------------------------------- | --------------------------- | ------------------ | | ioredis | @healthzkit/redis/ioredis | ioredisAdapter | | node-redis | @healthzkit/redis/redis | nodeRedisAdapter | | @upstash/redis | @healthzkit/redis/upstash | upstashAdapter |

All adapters are also re-exported from @healthzkit/redis if you depend on multiple clients.

Adapters

ioredis

import { ioredisAdapter } from "@healthzkit/redis/ioredis";
import Redis from "ioredis";

// Connection string (creates and reuses an internal client)
ioredisAdapter({ connectionString: "redis://localhost:6379" });

// Existing client
ioredisAdapter({ client: new Redis(process.env.REDIS_URL!) });

The command string is trimmed, split on whitespace, and passed to ioredis client.call(command, ...args) (default call("PING"); custom example "ECHO hello" → call("ECHO", "hello")). Repeated whitespace is ignored. Empty commands fail the check. Quoted arguments are not parsed.

node-redis

import { nodeRedisAdapter } from "@healthzkit/redis/redis";
import { createClient } from "redis";

nodeRedisAdapter({ connectionString: "redis://localhost:6379" });

const client = createClient({ url: process.env.REDIS_URL });
await client.connect();
nodeRedisAdapter({ client });

Upstash

import { upstashAdapter } from "@healthzkit/redis/upstash";
import { Redis } from "@upstash/redis";

upstashAdapter({
  url: process.env.UPSTASH_REDIS_REST_URL!,
  token: process.env.UPSTASH_REDIS_REST_TOKEN!,
});

upstashAdapter({ client: Redis.fromEnv() });

Options

Shared options on every adapter:

  • command — Command to run. Default "PING". For node-redis this is split on spaces and passed to sendCommand (e.g. "ECHO x"). For Upstash, non-PING commands use exec with parsed tokens.
  • metadata — Optional (client) => Promise<Record<string, unknown>>. Merged into the check result with latencyMs.

Connection options (mutually exclusive per adapter):

| Adapter | Create from credentials | Use existing client | | ---------- | ----------------------------------- | ------------------- | | ioredis | connectionString, redisOptions? | client | | node-redis | connectionString, redisOptions? | client | | Upstash | url, token | client |

Check result

On success:

{
  "status": "ok",
  "metadata": { "latencyMs": 12 }
}

On failure, status is "fail" and error is set (see healthzkit for how that rolls up into probe responses).

Development (this repo)

From the package directory:

vp install
vp test
vp pack

See the repo root AGENTS.md for Vite+ / vp conventions.