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

@sh1n4ps/plasma-client

v0.2.0

Published

IndexedDB engine, optimistic mutate, push/pull sync with rebase, and reactive live queries. Runs against any HTTP endpoint that speaks the plasma sync protocol.

Downloads

80

Readme

@sh1n4ps/plasma-client

Browser-side runtime for plasma. Owns the IndexedDB storage, the reactive engine live queries subscribe to, and the sync loop — outbox → push → pull → rebase → notify.

Install

pnpm add @sh1n4ps/plasma-client @sh1n4ps/plasma-core

Quick shape

import { createPlasmaClient, createWebSocketSubscription } from "@sh1n4ps/plasma-client"

const plasma = createPlasmaClient({
  schema, mutators,                                   // from @sh1n4ps/plasma-core
  dbName: "todos",
  endpoint: "/sync",                                   // your worker route
  schemaVersion: "v1",
  clientGroupID: getInstallId(),                       // persist yourself
  getContext: () => ({ userId: currentUser.id }),      // per-mutation ctx
  subscribe: createWebSocketSubscription({
    url: "wss://api/sync/coordinator",
    room: "global",
  }),
})

plasma.start()

// Reads
const todos = await plasma.db.select().from(todos)
const live = plasma.db.select().from(todos).where(eq(todos.done, 0)).live()
live.subscribe(rows => render(rows))

// Optimistic mutation (rebase v1 heals if the server rejects)
await plasma.mutate("createTodo", {
  id: plasma.newId(),
  title: "buy milk",
  updatedAt: Date.now(),
})

What lives here

  • createPlasmaClient — the top-level factory. Wires the IDB engine, outbox, cookie, identity, push, pull, rebase, and (optional) realtime subscription. Exposes db, mutate, newId, pullOnce, pushOnce, start, stop, flush.
  • createIdbEngine — the naive but honest AST evaluator. Uses idb under the hood. Also exports pauseNotifications / resumeNotifications which the sync client uses to silence reactive subscribers during a rebuild.
  • createWebSocketSubscription — auto-reconnecting WS client for the SyncCoordinator DO. Yields subscribe: (onPoke) => unsubscribe you plug straight into PlasmaClientOptions.subscribe.
  • baseStoreName, META_STORE, OUTBOX_STORE — the internal IDB store names, exported for tooling (a DevTools panel etc.).

Design notes

  • Rebase v1: every user table has a shadow _plasma_base_<name> store that mirrors server-canonical rows. After each pull the outbox drops confirmed mutations, then the optimistic view is rebuilt from base + replayed outbox. A mutation the server silently rejected (auth deny / errored mutator) heals on the next round-trip with no manual reset.
  • Inflight queue: pushes, pulls, and mutations are chained through a single-slot inflight promise so concurrent calls stay FIFO consistent with the outbox on disk.
  • newId(): pre-generate the mutation's id at the call site (before passing into args) so the optimistic and canonical runs agree.

Runtime footprint

Browser-only ESM with a single runtime dependency: idb.