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/crdt-automerge

v0.3.0

Published

Automerge CRDT backend for @homeostate/core

Readme

@homeostate/crdt-automerge

npm minzipped size downloads license

Automerge backend for @homeostate/core. It maps the synced state onto one key of an Automerge document (objects become maps, arrays lists, and strings ImmutableStrings or, where you choose, text), one Automerge change per write.

Install

npm install @homeostate/core @homeostate/crdt-automerge @automerge/automerge

@automerge/automerge 3.x is a peer dependency. It ships WebAssembly; for bundler setup see Automerge's documentation.

Usage

Automerge documents are immutable, so createAutomergeHandle holds the current one for the backend and your replication code to share:

import * as A from "@automerge/automerge";
import { createSyncEngine } from "@homeostate/core";
import {
  createAutomergeBackend,
  createAutomergeHandle,
} from "@homeostate/crdt-automerge";

const handle = createAutomergeHandle(A.init());
const engine = createSyncEngine(
  createAutomergeBackend(handle, "shared"),
  adapter,
);
engine.connect();

// Replication is yours to wire:
handle.subscribe(({ doc, local }) => {
  if (local) send(A.getLastLocalChange(doc));
});
onMessage((change) => handle.update((doc) => A.applyChanges(doc, [change])[0]));

handle.doc() returns the current document, handle.change(fn) applies a local change, and handle.update(fn) replaces the document with the result of any Automerge call. See the documentation for details.

To let an automerge-repo Repo store and sync the document instead, pass one of its DocHandles:

createAutomergeBackend(await repo.find(url), "shared");

Strings are ImmutableString values, so concurrent writes keep one of them. Pass text to store chosen strings as Automerge text, whose concurrent edits merge character by character:

createAutomergeBackend(handle, "shared", {
  text: (path) => path[0] === "todos" && path[2] === "title",
});

To persist the document, pass createAutomergePersistable(handle) to createPersistence, or use a Repo's storage adapter; see the persistence guide.

License

MIT — see LICENSE. Includes code derived from zustand-middleware-yjs; see THIRD_PARTY_NOTICES.md.