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

@storesjs/stores

v0.11.0

Published

Stores provides a minimal, reactive state layer that runs with or without React.

Readme

Stores

Stores provides a minimal, reactive state layer that runs with or without React.

It defines three types of runtime-evaluated stores—base, derived, and query—each representing a distinct state type: local, computed, or asynchronously fetched. Stores track dependencies at runtime, evaluate lazily, and clean up automatically when unused.

All stores expose a consistent interface and can be used both inside and outside React. Each store is a node. Together they form a composed graph.

  • Base stores define synchronous local state with explicit update methods.
  • Derived stores compute values from other stores and re-run only when inputs change.
  • Query stores fetch and cache async data, refetching when reactive parameters change.

All store types expose a stable store object with .getState() and .subscribe(), plus optional support for persistence. In the React build, stores are also callable hooks. In the vanilla build, stores remain plain store objects. They compose naturally, interoperate cleanly, and scale as application complexity grows.

Runtime Modes

The root import is mode-aware:

  • React web apps use @storesjs/stores by default.
  • React Native apps use @storesjs/stores; the react-native package condition selects the native build.
  • Vanilla apps use @storesjs/stores with the vanilla package condition enabled.

For TypeScript vanilla projects, use a condition-aware resolver and add the same condition to tsconfig.json:

{
  "compilerOptions": {
    "module": "ESNext",
    "moduleResolution": "bundler",
    "customConditions": ["vanilla"]
  }
}

Base Store

A base store defines local state along with an interface for reading and updating that state.

export const settingsStore = createBaseStore<Settings>(set => ({
  currency: 'USD',
  setCurrency: currency => set({ currency }),
}));

In React, subscribe to values with selectors:

const currency = settingsStore(s => s.currency);

Outside React:

settingsStore.getState().currency;
settingsStore.subscribe(selector, listener, options);

Enable persistence per store:

createBaseStore<Settings>(set => ({ ... }), {
  storageKey: 'settings',
  partialize: state => ({ currency: state.currency }),
});

You can also export actions as a stable object:

export const settingsActions = createStoreActions(settingsStore);

Derived Store

Derived stores compute values from other stores. The $ accessor tracks dependencies at runtime:

export const totalStore = createDerivedStore($ => {
  const { currency } = $(settingsStore);
  const { subtotal, tax } = $(cartStore);
  return formatTotal(currency, subtotal, tax);
});

If currency, subtotal, or tax change, the store re-computes.

If the store is not observed, nothing runs.

Query Store

Query stores manage remote data. They fetch, cache, and revalidate based on reactive parameters:

export const accountStore = createQueryStore<Account, Params>({
  fetcher: fetchAccount,
  params: {
    userId: $ => $(authStore).userId,
  },
  staleTime: time.minutes(10),
});

When userId changes, the store refetches. If unobserved, it remains idle.

Use it in React:

const account = accountStore(s => s.getData());

Or imperatively:

accountStore.getState().fetch();

Query stores support full customization: extended local state, manual cache control, configurable staleness and retry behavior, and optional persistence.

They deduplicate fetches across consumers and compute stable query keys automatically.

Store Interface

All stores implement the same store-object API:

store.getState()
store.setState() // Except for derived stores
store.subscribe(selector, listener, options?)

In the React build, stores are also callable hooks:

store()
store(selector, equalityFn?)

Composed Example

export const currencyFormatterStore = createDerivedStore($ => {
  const { currency, locale } = $(settingsStore);
  return new Intl.NumberFormat(locale, {
    currency,
    style: 'currency',
  });
});
export const accountBalanceStore = createDerivedStore($ => {
  const balance = $(accountStore).getData()?.balance ?? 0;
  const formatter = $(currencyFormatterStore);
  return formatter.format(balance);
});
function AccountSummary() {
  const balance = accountBalanceStore();
  return <Text>Balance: {balance}</Text>;
}