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

@tasfer/provider-core

v0.1.4

Published

Transport-agnostic sync protocol that connects a @tasfer/editor Doc to any pipe (the shared core every provider builds on).

Readme

@tasfer/provider-core

The transport-agnostic sync protocol behind every @tasfer/editor provider. Pair a CRDT Doc with a pipe and the two replicas converge: version vectors are exchanged, missing operations are sent, and new ones stream in real time after catch-up.

Most apps never import this directly — they install a transport package (@tasfer/provider-webrtc, @tasfer/provider-relay) that wraps it. Reach for it when you want to sync over something of your own.

Install

npm install @tasfer/editor @tasfer/provider-core

Usage

import { createProvider } from "@tasfer/provider-core";

const provider = createProvider({ doc: editor.doc, transport });

provider.on("sync", ({ connected, peers }) => {
  status.textContent = connected ? `${peers} peer(s)` : "offline";
});

Bring your own transport

A transport only has to discover peers and move opaque bytes between them. Implement Transport and you can sync over a relay, a BroadcastChannel, a file watcher, or your own backend:

interface Transport {
  connect(): Promise<void> | void;
  onPeerJoin(cb: (peer: TransportPeer) => void): () => void;
  onPeerLeave(cb: (peerId: string) => void): () => void;
  getPeers(): TransportPeer[];
  destroy(): void;
}

Each TransportPeer exposes send(bytes), onMessage(cb), and onClose(cb). Framing is the transport's problem; ordering and losslessness are its contract.

createBroadcastChannelTransport ships in the box — same-origin tab-to-tab sync, and a working reference implementation to read.

Presence

Presence is ephemeral state that travels alongside the document but is never persisted. The protocol routes whatever object you publish:

provider.presence.set({ name: "Ada", color: "#1db984" });

provider.presence.on("change", (peers) => {
  avatars.render(peers.map((p) => p.state.name));
});

To turn presence into remote carets and selections, bind it to the editor with the helper from the /cursors subpath — kept out of the base entry so a non-editor consumer of the protocol pays no editor coupling:

import { bindPresenceCursors } from "@tasfer/provider-core/cursors";

const stop = bindPresenceCursors(editor, provider, {
  user: { peerId, name: "Ada", color: "#1db984" },
});

Documentation

tasfer.app/docs/editor/collaboration

License

MIT