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

@ceptesoft/local-first-store

v0.1.0

Published

Offline-first persistence plumbing: debounced and version-stamped storage decorators (zustand-persist compatible) plus keyed-collection upsert/remove helpers. Zero dependencies.

Readme

@ceptesoft/local-first-store

Offline-first persistence plumbing for stores that keep server data locally for instant reads: debounced and version-stamped storage decorators, plus immutable keyed-collection helpers. Zero dependencies — the decorators are structurally compatible with window.localStorage and the sync subset of zustand's StateStorage, but zustand is not required.

Extracted from a production PWA (CepteCari) where customers/suppliers/ products live in a persisted store: writing a large JSON snapshot to localStorage on every keystroke janks the UI, and rehydrating a snapshot written by an older app version crashes on schema drift.

Scope boundary: persistence plumbing only — no sync engine, no conflict resolution.

Install

npm install @ceptesoft/local-first-store

Quickstart (with zustand persist)

import { create } from "zustand";
import { persist, createJSONStorage } from "zustand/middleware";
import { debounceStorage, versionStorage, upsertById, removeById } from "@ceptesoft/local-first-store";

const PERSIST_VERSION = 4;

type Customer = { id: string; name: string };
type State = {
  version: number;
  customers: Customer[];
  upsertCustomer: (c: Customer) => void;
  removeCustomer: (id: string) => void;
};

const useStore = create<State>()(
  persist(
    (set) => ({
      version: PERSIST_VERSION,
      customers: [],
      upsertCustomer: (c) => set((s) => ({ customers: upsertById(s.customers, c) })),
      removeCustomer: (id) => set((s) => ({ customers: removeById(s.customers, id) })),
    }),
    {
      name: "app-data",
      storage: createJSONStorage(() =>
        versionStorage(debounceStorage(window.localStorage, 400), PERSIST_VERSION)
      ),
    }
  )
);

Flush pending writes when the tab closes:

const storage = debounceStorage(window.localStorage, 400);
window.addEventListener("pagehide", () => storage.flush());

API

debounceStorage(base, debounceMs)DebouncedStorage

Coalesces rapid setItem calls into one write after debounceMs of quiet. While a write is pending, getItem returns the pending value (read-your-writes) and removeItem cancels it. flush() writes immediately.

versionStorage(base, version, options?)SyncStringStorage

getItem returns null (instead of the raw snapshot) when the persisted JSON fails to parse or its version stamp doesn't equal version — the store falls back to initial state instead of crashing on stale schemas. The stamp is read from parsed.state.version by default; override with options.getVersion.

upsertById(list, item) / removeById(list, id)

Immutable helpers for { id: string } collections. upsertById inserts new ids at the front (newest-first) and replaces existing ids in place so visible ordering doesn't jump.