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

@li3/store

v0.1.76

Published

Manage state and logic in one place.

Readme

@li3/store

Manage state and logic in one place.

What is a store?

Stores are a concept used in many different languages and frameworks.

In this library, a store is a place for adding methods and keeping track of state in one unit. Methods, sometimes called actions, can change the internal state of a store.

The internal state is stored as a Signal. To access that state, use selectors.

Usage

First declare a store in a module

// count-store.js
import { createStore } from '@li3/store';

export default createStore(
  { count: 0 },
  {
    add(state, amount) {
      state.count += amount;
    },
    remove(state, amount) {
      state.count -= amount;
    }
  }
);

Then import the store and dispatch actions:

import countStore from './count-store.js';

// it's safe to import the same store many times
const { select, store } = countStore;

store.add(10)
store.remove(5);

// counter is a computed value
const counter = select((s) => s.count);

Transactions

Stores can push multiple changes and run side effects within a single update cycle. That can be done with a .transaction() call in the store:

import countStore from './count-store.js';

const { store, transaction, events } = countStore;

events.addEventListener('commit', (state) => {...})

transaction(async () => {
  await store.increment(1);
  await store.increment(10);
  await store.decrement(5);
});

All intermediate states are not propagated to any selector. When all actions are completely dispatched, the state is pushed into the store and all computed values reflect the changes.