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

@opentf/esrun-valkey

v0.1.1

Published

Valkey client and runtime:db driver for esrun.

Downloads

509

Readme

@opentf/esrun-valkey

A Valkey driver for ES Runtime: a runtime:db backend and a Valkey client, written entirely in JavaScript over runtime:net. There is no native code in this package, and none was added to the runtime for it.

npm install @opentf/esrun-valkey
import { connect } from "runtime:db";
import { driver } from "@opentf/esrun-valkey";

const v = await connect("valkey://localhost", { driver });

await v.set("session:42", "ada", { ex: 3600 });
await v.get("session:42");                    // "ada"
await v.hset("user:42", { name: "ada", age: "36" });
await v.hgetall("user:42");                   // { name: "ada", age: "36" }

await v.close();

Valkey kept Redis's protocol, so this package is built on @opentf/esrun-redis rather than beside it: the same connection, pool, pipelines, MULTI/EXEC, pub/sub, blocking commands, cluster and Sentinel clients, under Valkey's names. The Redis driver's documentation describes all of it; everything there applies here with valkey for redis.

Connection strings

valkey://[[username][:password]@]host[:port][/db][?option=value], and valkeys:// for TLS from the first byte. redis:// and rediss:// are taken too, so a connection string written for Redis keeps working unchanged.

Drivers

| Export | Opens | | --- | --- | | driver | One connection; pool: true makes it a pool with the same surface | | valkeyCluster | A cluster client: a pool per node, routed by slot | | valkeySentinel | A connection to the primary that Sentinel names |

import { valkeyCluster } from "@opentf/esrun-valkey";

const cluster = await connect("valkey://10.0.0.1:7001", {
  driver: valkeyCluster,
  seeds: ["valkey://10.0.0.2:7001"],
});

What they open reports backend as valkey (valkey-cluster for a cluster), and errors name Valkey. The classes are exported as ValkeyConnection, ValkeyPooled and ValkeyCluster; they are the Redis package's own classes, so instanceof holds under either name.

Valkey-only commands

A command without a helper is one call away, Valkey-only ones included:

await v.call(["DELIFEQ", "lock:job", token]);   // Valkey 9