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

@babbling/signals

v0.0.1

Published

A reactive state management tool

Readme

Project Status

:scientist: Experimental

I'm using this in personal projects. There are rough edges and the API is constantly evolving. I might abandon it.

Philosophy

  • State changes should only happen in response to IO events or errors.
  • Changes should be batched and atomic.
  • Gather, Plan, Execute: Effects run by gathering inputs, planning a change, and executing the plan.

Installing

npm install --save @babbling/signals

To use the bleeding edge version from the main branch, use the @rc tag (release candidate):

npm install --save @babbling/signals@rc

Usage

Everything is built around atoms. Atoms are reactive values that can be read and updated.

import { atom, swap, get } from '@babbling/signals';

const $count = atom(0);

console.log(get($count)); // 0

const increment = action((amount) => {
  swap($count, get($count) + amount);
});

Updates are executed in "actions", a batch of changes that apply all at once or not at all.

The Signal API is exported for advanced cases, such as custom bindings or watchers. See the React binding for an example.

External Sources

For data sources that change over time, you can bind with the external(...) API:

const $visibility = external(
  () => document.visibilityState,
  (onChange) => {
    document.addEventListener('visibilitychange', onChange);
    return () => document.removeEventListener('visibilitychange', onChange);
  }
);

Behaviors

Behaviors are the effect system. They are writable values inside actions and run when the action commits.

const useDarkTheme = action(() => {
  swap(theme, 'dark');
});

const theme = behavior((value: string) => {
  localStorage.setItem('theme', value);
});

Bindings

A few bindings are exposed for popular packages. They're optional and assume you've already installed the package.

React

// React
import { atom } from '@babbling/signals';
import { useValue } from '@babbling/signals/react';

const $count = atom(0);

export function Counter() {
    const count = useValue($count)
    return <p>Count: {count}</p>
}

Immer

import { atom, action } from '@babbling/signals';
import { update } from '@babbling/signals/immer';

const $state = atom({ count: 0 });

export const increment = action(() => {
  update($state, (draft) => {
    draft.count += 1;
  });
});