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

@homeostate/tool-simulator

v0.2.0

Published

Test homeostate peers on a simulated network with latency, drops, reordering and partitions, and check that they converge

Readme

@homeostate/tool-simulator

npm minzipped size downloads license

Test that peers synced by @homeostate/core converge. It runs several peers, each a store, a backend and a sync engine, on a simulated network with latency, dropped and reordered messages and partitions, on virtual time, and checks that every peer ends up with the same state.

Install

npm install -D @homeostate/tool-simulator

It works with any test runner: a failed check throws an error that says where peers differ.

Usage

import * as Y from "yjs";
import { createStore } from "zustand/vanilla";
import { createYjsBackend, createYjsPersistable } from "@homeostate/crdt-yjs";
import { createZustandAdapter } from "@homeostate/store-zustand";
import { createNetwork } from "@homeostate/tool-simulator";

const network = createNetwork({ latency: [5, 50], seed: 42 });
const stores = [0, 1, 2].map(() => {
  const doc = new Y.Doc();
  const store = createStore(() => ({ todos: [] }));
  network.addPeer({
    adapter: createZustandAdapter(store),
    backend: createYjsBackend(doc, "shared"),
    doc: createYjsPersistable(doc),
  });
  return store;
});
await network.settle();

const [alice, bob] = network.peers;
network.disconnect(alice, bob);
stores[0].setState({ todos: [{ title: "milk" }] });
stores[1].setState({ todos: [{ title: "bread" }] });

network.heal();
await network.settle();
network.expectConverged();

Each peer's doc is its backend's document as binary updates, from the CRDT package's create*Persistable: that is what the network carries. settle() delivers every message on its way, and expectConverged() throws unless every peer's store and document agree.

runRandomized drives random edits, link cuts and reconnections across a fresh network, then checks convergence and names the seed of a run that fails:

await runRandomized({
  createPeer: (index) => makePeer(index),
  network: { latency: [0, 20], reorder: true, dropRate: 0.1 },
});

See the documentation for every network control and what convergence compares.

License

MIT — see LICENSE.