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

js-wavela

v1.0.1

Published

A simple JavaScript state management library.

Readme

js-wavela

A simple javascript state management library without any complexity. You have an action and a state attached to that action. Whenever a change is dispatched all listeners will get the updated state. Isn't this what every other state management does? Yes, but this library makes this process really simple. Check out examples below.

There is no concept of store. Everything is an action and against an action there is a state attached to it. To subscribe to an action just use subscribe method.

import Store from "js-wavela";
const callback = (state: YourStateInterface) => { /* Do something with this state */ }
Store.subscribe<YourStateInterface>("Action_Name", callback);
Store.dispatch("Action_Name", {property_in_state_to_change: "New Value"});
Store.unsubscribe("Action_Name", callback);

Initial State

If you don't provide initial state in Store.subscribe method state will be an object without any properties. But if same action is initialized with two different initial states, new state will merge with existing state and all the listeners will be called with the updated state.

Store.subscribe("shops", callback1, {names: ["1"]});

At this point state is initialized against shops actions and state is as follows

{
    names: ["1"]
}

Now if we subscribe again to the same action with the initial state

Store.subscribe("shops", callback2, {addresses: ["some_address"]});

State for shops is now

{
    names: ["1"],
    addresses: ["some_address"]
}

After the second subscribe call to shops, all the listeners will be called with the updated state (in this case callback1) except for callback2. Assumption here is that, since callback2 came along with the updated state it already knows whats up as subscribe method also return the updated state.

Unsubscribe

To unsubscribe listening to an action, just use Store.unsubscribe and pass the action name and callback. Callback's reference should be the same as it searches for that callback in the array. Note that if there are no more listeners for a particular action (meaning all of them unsubscribed), state will be deleted from the store.

Feel free to contribute or suggest any thing. Thank you.