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

@crdt-sync/server

v0.3.5

Published

WebSocket relay server for crdt-sync

Downloads

37

Readme

@crdt-sync/server

A zero-dependency* WebSocket relay server for the crdt-sync CRDT library.

*The only runtime dependency is the ws library.

How it works

The relay is intentionally simple — it maintains no server-side state. All CRDT merge logic runs inside the Wasm StateStore in each browser tab.

Client A ──► Relay ──broadcast──► Client B
                   └──broadcast──► Client C

When Client A writes to its CRDT store, the resulting envelope (a compact operation log entry) is sent to the relay as a JSON array. The relay broadcasts that array to every other connected client, which then applies the envelopes to their local Wasm stores.

Installation

npm install @crdt-sync/server

Usage

CLI

# Start on the default port (8080)
npx crdt-sync-server

# Use a custom port
npx crdt-sync-server --port 3001

Programmatic

import { createRelay } from '@crdt-sync/server';

const relay = createRelay({
  port: 8080,
  host: '0.0.0.0',         // optional, default '0.0.0.0'
  onListening: (port) => {  // optional callback
    console.log(`Relay ready on port ${port}`);
  },
});

// Shut down gracefully
await relay.close();

Protocol

| Direction | Format | Description | |-----------------|------------------------------------------|---------------------------------------------------| | Client → Server | JSON string of string[] | Array of CRDT envelope JSON strings to broadcast | | Server → Client | Same JSON string (forwarded as-is) | Sent to all clients except the sender |

Example message

["{\"type\":\"lww\",\"key\":\"speed\",\"value\":100,\"ts\":1708801200000,\"nodeId\":\"client-abc123\"}"]

Self-hosting / Custom relay

You don't need this package to run the relay. Any WebSocket server that implements the protocol table above will work. Here's a minimal Node.js example using the ws library directly:

import { WebSocketServer, WebSocket } from 'ws';

const wss = new WebSocketServer({ port: 8080 });

wss.on('connection', (socket) => {
  socket.on('message', (raw) => {
    // Broadcast to all other clients
    wss.clients.forEach((client) => {
      if (client !== socket && client.readyState === WebSocket.OPEN) {
        client.send(raw.toString());
      }
    });
  });
});