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

store-thing

v0.3.1

Published

A reactive store backed by localStorage/sessionStorage, with immutable updates, typed events, and cross-tab sync

Readme

store-thing

A reactive store persisted to localStorage or sessionStorage: immutable draft-style updates, typed change events, and cross-tab sync. State must be JSON-serializable — that is what survives the storage round-trip.

npm install store-thing
import { Store } from "store-thing";

const store = new Store("counter", { count: 0 });
// persisted under localStorage key "store-counter"; an existing value wins over the initial one

// subscribe: immediate call with current state, then every change
const sub = store.subscribe((state) => console.log(state.count));

// update a draft copy; the store persists and emits the result
store.update((draft) => { draft.count += 1; });

store.get();   // { count: 1 } — treat as read-only; change via update()
store.reset(); // back to the initial value

sub.dispose(); // or `using sub = store.subscribe(…)`

API

  • new Store(id, initValue, { storage? })storage is "local" (default) or "session". The value in storage wins over initValue, which is only written when the key is empty.
  • get(): T — the current state, from an in-memory cache (storage is only read at construction and on cross-tab events).
  • update(draft => void) — mutate a structuredClone of the state; the result is persisted and emitted. The previous state object is never mutated.
  • reset() — persist and emit a fresh copy of initValue.
  • on("change", state => void) / subscribe(state => void) — listen for changes; subscribe also calls back immediately with the current state. Both return a handle with dispose() and [Symbol.dispose] (see @rupertsworld/disposable).
  • Store is a typed EventTarget (via @rupertsworld/event-target): store.addEventListener("change", (e) => e.state) works, with full typing and native options (once, signal, …).
  • Cross-tab sync — for localStorage-backed stores, a write from another tab updates the store and emits change (via the window storage event; sessionStorage is per-tab, so no sync there). dispose() detaches the window listener — only needed for stores that don't live as long as the page.

Changes in 0.3.0

Rebuilt on @rupertsworld/event-target and @rupertsworld/disposable; Immer replaced by structuredClone (same update(draft => …) API, one less dependency); get() returns T (not T | undefined) from an in-memory cache; cross-tab sync added; ESM only, CommonJS build dropped.