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

loro-repo

v0.12.1

Published

Draft TypeScript definitions for the LoroRepo orchestrator.

Readme

LoroRepo TypeScript bindings

LoroRepo is the collection-sync layer above Flock. It coordinates document metadata and document bodies so apps can:

  • fetch metadata first, then open document bodies on demand,
  • reuse one API across centralized servers, Durable Objects, and peer meshes,
  • keep repo semantics predictable with explicit soft-delete and purge flows.

What you get

  • Metadata-first coordinationrepo.listDoc() and repo.watch() expose LWW metadata quickly.
  • On-demand documentsopenPersistedDoc() gives a repo-managed LoroDoc that can sync once or join a live room; openDetachedDoc() gives an isolated snapshot.
  • Pluggable adapters – provide your own TransportAdapter and StorageAdapter (or use built-ins below).
  • Consistent events – every event includes by: "local" | "sync" | "live".
  • Deletion lifecycle – soft delete (deleteDoc) and hard purge (purgeDoc / gcDeletedDocs) are separate and explicit.

Quick start

import { LoroRepo } from "loro-repo";
import { BroadcastChannelTransportAdapter } from "loro-repo/transport/broadcast-channel";
import { IndexedDBStorageAdaptor } from "loro-repo/storage/indexeddb";

type DocMeta = { title?: string; tags?: string[] };

const repo = await LoroRepo.create<DocMeta>({
  transportAdapter: new BroadcastChannelTransportAdapter({ namespace: "notes" }),
  storageAdapter: new IndexedDBStorageAdaptor({ dbName: "notes-db" }),
});

await repo.sync({ scope: "meta" });
await repo.upsertDocMeta("note:welcome", { title: "Welcome" });

const handle = await repo.openPersistedDoc("note:welcome");
await handle.syncOnce();
const room = await handle.joinRoom();
handle.doc.getText("content").insert(0, "Hello from LoroRepo");
handle.doc.commit();
room.unsubscribe();
await repo.unloadDoc("note:welcome");

Using the API

  • Create a repo with await LoroRepo.create<Meta>({ transportAdapter?, storageAdapter?, docFrontierDebounceMs? }).
  • Swap transport later with await repo.setTransportAdapter(adapter).
  • Check adapter availability via repo.hasTransport() and repo.hasStorage().
  • Choose sync lanes using repo.sync({ scope: "meta" | "doc" | "full", docIds? }).
  • Work with docs through openPersistedDoc, openDetachedDoc, joinDocRoom, unloadDoc, and flush.
  • React to changes with repo.watch(listener, { docIds, kinds, metadataFields, by }).
  • Shutdown cleanly by calling await repo.destroy().

Built-in adapters

  • BroadcastChannelTransportAdapter (src/transport/broadcast-channel.ts)
  • WebSocketTransportAdapter (src/transport/websocket.ts)
  • IndexedDBStorageAdaptor (src/storage/indexeddb.ts)
  • FileSystemStorageAdaptor (src/storage/filesystem.ts)

Core API surface

Lifecycle

  • await LoroRepo.create<Meta>(options)
  • await repo.sync(options?)
  • await repo.destroy()

Metadata

  • await repo.upsertDocMeta(docId, patch)
  • await repo.getDocMeta(docId)
  • await repo.listDoc(query?)
  • repo.getMeta() / repo.getRawMeta()

Documents

  • await repo.openPersistedDoc(docId)
  • await repo.openDetachedDoc(docId)
  • await repo.joinDocRoom(docId, params?)
  • await repo.unloadDoc(docId)
  • await repo.flush()

Deletion & retention

  • await repo.deleteDoc(docId, { deletedAt?, force? })
  • await repo.restoreDoc(docId)
  • await repo.purgeDoc(docId)
  • await repo.gcDeletedDocs({ minKeepMs?, now? })

Events

  • const handle = repo.watch(listener, filter?)
  • handle.unsubscribe()

Doc deletion lifecycle

  1. Soft delete (deleteDoc) writes ts/<docId> and keeps metadata/doc snapshots available.
  2. Retention window (deletedDocKeepMs) controls when GC can purge.
  3. Hard purge (purgeDoc / gcDeletedDocs) removes metadata/frontiers/tombstone and drops local doc snapshots.
  4. Legacy cleanup: during purge, legacy ld/<docId>/* rows are also removed when present.

Commands

| Command | Purpose | | --- | --- | | pnpm --filter loro-repo typecheck | Runs tsc with noEmit. | | pnpm --filter loro-repo test | Runs Vitest suites. | | pnpm --filter loro-repo check | Runs typecheck + tests. |

Set LORO_WEBSOCKET_E2E=1 when running websocket end-to-end specs.

Examples

  • P2P Journal (examples/p2p-journal/) – Vite + React demo with BroadcastChannel + IndexedDB.
  • Sync script (examples/sync-example.ts) – metadata/document synchronization walkthrough.

Contributing

Follow Conventional Commits, run pnpm --filter loro-repo check before opening a PR, and keep prd/ docs aligned with behavior changes.