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

@gomani/data

v0.5.0

Published

Offline-first, local-first data: an IndexedDB store, optimistic mutations, and a sync engine.

Readme

@gomani/data

Offline-first, local-first data with a built-in sync engine for Gomani.

Offline is the baseline (P5): the local device is authoritative, the network is opportunistic. Writes are optimistic and instant, the app is fully usable disconnected, and a sync reconciles when connectivity returns. The main entry is server-safe (the sync server half + shared types); the client store lives at @gomani/data/client.

The client store

import { createStore, createFetchTransport, online, watchOnline } from '@gomani/data/client';

const store = createStore({
  collections: ['todos'],
  transport: createFetchTransport('/_gomani/sync'),
});
const todos = store.collection<Todo>('todos');

await todos.put({ id: '1', text: 'Sound the drum', done: false }); // optimistic + queued + persisted
todos.get('1'); // synchronous read from the local cache
todos.items.value; // a reactive snapshot — bind it in an island

await store.sync(); // push queued mutations, pull server changes, reconcile
store.pending.value; // mutations still awaiting sync
watchOnline((isOnline) => isOnline && store.sync()); // sync on reconnect

The sync server

import { createSyncHandler, createMemoryStore } from '@gomani/data';

const sync = createSyncHandler({ store: createMemoryStore() });
// mount it in app/server.ts:
export default (req) => (new URL(req.url).pathname === '/_gomani/sync' ? sync(req) : null);

Push/pull with a monotonic cursor; conflicts resolve by last-write-wins (pluggable — a Yjs CRDT is a later drop-in). The in-memory store is the local default; a Postgres-backed ServerStore is a drop-in for production.

Service worker

import { generateServiceWorker } from '@gomani/data'; // used by `gomani build` to emit sw.js
import { registerServiceWorker } from '@gomani/data/client'; // call it in an island

gomani build emits sw.js precaching the shell (routes + eager runtime + CSS): cache-first for hashed assets, network-first with an offline fallback for navigations — so the app loads offline after the first visit.

License

MIT © Venancio Gomani / Kwacha Kulture.