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

@next-model/valkey-connector

v1.2.0

Published

Valkey connector for next-model. Extends @next-model/redis-connector — Valkey is wire-compatible with Redis.

Downloads

466

Readme

@next-model/valkey-connector

@next-model/core connector for Valkey, the open-source fork of Redis. Implemented as a thin extension of @next-model/redis-connector.

Why a separate package?

Valkey is wire-compatible with the Redis protocol — the same node-redis client, the same commands, the same HASH-per-row + ZSET-of-ids storage layout. So at the time of writing, ValkeyConnector is functionally identical to RedisConnector.

It exists as its own publishable name for two reasons:

  1. Discoverability. Apps that target Valkey can install the package whose name matches their database.
  2. Forward compatibility. Valkey ≥ 8.x is shipping features that aren't in upstream Redis (JSON, vector, improved clustering). Future Valkey-only overrides will land here without bloating redis-connector.

If you're targeting Redis itself, use @next-model/redis-connector directly.

Installation

pnpm add @next-model/valkey-connector redis
# or: npm install @next-model/valkey-connector redis

Constructing the connector

import { ValkeyConnector } from '@next-model/valkey-connector';

const connector = new ValkeyConnector({
  client: { url: 'valkey://valkey-host:6379' },
});
await connector.connect();

Pass an optional extras: { schema } second arg to attach a DatabaseSchema (from @next-model/core's defineSchema(...)) so Model({ connector, tableName: 'users' }) can infer per-table props at the type level — purely for Model inference, since Valkey enforces no DB schema at runtime.

const connector = new ValkeyConnector({ client: { url: '...' } }, { schema });

The constructor signature, runtime API, and storage layout are otherwise identical to RedisConnector's — see its README for the full surface (filter operators, transactions, schema DDL, …).

Testing matrix

CI runs the shared runModelConformance suite against a real valkey/valkey:8 service container.

Locally, point at any Valkey-compatible server (Valkey, Redis, KeyDB, Dragonfly, …):

VALKEY_URL=redis://127.0.0.1:6379 pnpm --filter @next-model/valkey-connector test

Changelog

See HISTORY.md.