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

@openknot-ts/redis-replication

v0.0.6-preview

Published

Redis implementation of the OpenKnot replica store and replication channel over consumer-owned clients.

Readme

@openknot-ts/redis-replication

Implements the replicaStore and replicationChannel contracts of @openknot-ts/replication over node-redis clients the application already manages.

Usage

import { redisReplicaStore, redisReplicationChannel } from "@openknot-ts/redis-replication/wire";

export const replicaStorage = redisReplicaStore({
  requirements: { redis },
  commands: ({ redis }) => redis.commands,
  connection: ({ redis }) => redis.connection.commands,
});

export const replicaChannel = redisReplicationChannel({
  requirements: { redis },
  connections: ({ redis }) => redis,
  connection: ({ redis }) => redis.connection.subscriber,
});

API

| Entry | Export | Description | | --- | --- | --- | | /wire | redisReplicaStore({ requirements?, commands, connection?, options? }) | The store. options(dependencies) returns ReplicaStoreOptions: { prefix, tombstoneTtl, encode, decode }. | | /wire | redisReplicationChannel({ requirements?, connections, connection, channel? }) | The channel; connection watches the subscriber client, channel is a string or (dependencies) => string. | | root | redisReplicationChannelOf(connections, { connection, channel? }) | The channel over clients directly. | | root | redisReplicaStoreOf(commands, options?) | The store over a client directly. |

Pass connection (such as redis.connection.commands from @openknot-ts/redis-client) so the replication learns of an outage at once; without it, commits, shared reads and stop() can wait for a held command. See the replication README.

Store

  • One Lua script applies a batch atomically: a state is stored when newer than the stored state and tombstone, a delete when at least as new.
  • Deletes leave tombstones that expire after tombstoneTtl (one hour by default).
  • Orders are non-negative integers below 10^20, or strings, which sort after integers.
  • A keyspace shares one hash tag, so it stays in one cluster slot. The marker is a hash; runId is the server's run_id.
  • States are JSON unless encode/decode are given.
  • Fenced apply, mark and every clear compare the marker's holder inside their script and reject with ReplicaFenced. An unfenced mark is one HSET, keeping the stored holder.
  • Scripts run through EVALSHA and fall back to EVAL on NOSCRIPT.
  • clear and drop walk the keyspace with SCAN and UNLINK; clear keeps the marker, drop removes it.

Channel

  • JSON messages on openknot:replication, or channel. Bigint keys and orders keep their type.
  • Invalid payloads are dropped. The subscriber client's connection reports the subscription lost and restored.

Example and tests

pnpm --filter @openknot-ts/redis-replication example runs two instances sharing roles; pnpm --filter @openknot-ts/redis-replication test:redis runs the integration tests against REDIS_URL. Both use the clients from examples/native.ts.