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 🙏

© 2025 – Pkg Stats / Ryan Hefner

store-up

v1.1.1

Published

Yet another state management tool

Readme

Yet another state management tool

  • Simple - No need for reducers, action creators, dispatchers or other frightful concepts.
  • Recursive - Not only main state object has Update function, that triggers re-rendering of components, but also any inner object property.
  • Debugable - You can simply log/get current state or hole state change history to debug your project.

Instalation

npm

npm i store-up

yarn

yar add store-up

Usage

First, include the state manager in your code

import Up from 'store-up'

Up is a function, that takes two parameters: initial state and a function, that takes the current state and render components basing on that state (store)

Up(
    {counter: 0, options: {step: 1}},
    store => {
    document.body.innerHTML = `
    	<div>
        	<h1>Count: ${store.counter}</h1>
        </div>
    `
    }
)

To change current state, we should call method "up", and pass object with needed changes

store.up({counter: store.counter + store.options.step})

It will automatically update the state and recall function, passed as the second parameter to Up function, with updated state (store)

If your state has an object as any nested parameter, that object is also updatable

store.options.up({step: 2})

Example

Here I used functional approach, to make it more concise

import React from 'react'
import ReactDOM from 'react-dom'

import Up from 'store-up'

const increment = store => store.up({counter: store.counter + 1})

const Label = store => <h1>Counter: {store.counter}</h1>

const Btn = store => <button onClick={() => increment(store)}>Plus</button>

const Main = store => <div>
    {Label(store)}
    {Btn(store)}
</div>

Up(
    {counter: 0},
    store => {
        ReactDOM.render(
            Main(store),
            document.querySelector("#app")
        )
    }
)

History

If you want to console.log history of state changes or only last state, you can pass two additional parameters to imported Up function.

Up(initialState, function callback[, withHistory[, log]])

The third parameter decides whether to keep hole history or only the last one (false by default)

The fourth parameter decides whether or not to console.log the history or the last state (false by default)

So if we call Up function in the example above like this

Up(
    store,
    store => render(store),
    true,
    true
)

On every click it will console.log something like

**click** //logs [{counter: 1}]
**click** //logs [{counter: 1}, {counter: 2}] etc

If instead of logging you want to manually handle the history array, you can call getHistory method, to get it.

store.getHistory()