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 🙏

© 2024 – Pkg Stats / Ryan Hefner

observable-state-store

v1.0.0

Published

simple observable state store

Downloads

3

Readme

observable-state-store

Simple observable state store.

Travis build status Code Climate Test Coverage Dependency Status devDependency Status

Features

  • Clear state definitions
  • Clear action definitions
  • Observable
  • Simple to use and maintain

Installation

npm i --save observable-state-store

Usage

import Store from 'observable-state-store'

// define state
const state = {
  count: 0
}

// define actions
const actions = {
  inc: (state, number) => Object.assign({}, state, {count: state.count + number})
}

// create store
const store = new Store({state, actions})

// subscribe to the state
const subscription = store.subscribe((newState, oldState) => {
  if (newState.count > oldState.count) {
    console.log('count inc!')
  }
});

// execute action
store.actions.inc(-2); // nothing
store.actions.inc(3); // print 'count inc!'

// stop subscription
subscription.stop();
store.actions.inc(2); // nothing 

APIs

Store

constructor(options)

options is an object with fields

  • state
  • actions

state can be anything, but we recommend to use Immutable.js or similar things as your state.

actions are functions grouped into an object. The signature of any action is

function(oldState, ...args): newState

Inside the action body, you should not modify the old state directly. Instead, you should create and return an new state.

subscribe(observer): subscription

Subscribe to the store, and get notified by any execution of the actions.

observer is an function with the signature

function(newState, oldState)

You should not modify either newState or oldState.

Call subscription.stop() to stop the subscription.

actions

actions are mapped from the actions you passed into the constructor with new signature

function(...args)

For example, if you passed into constructor such an action

{
  inc: (state, number) => Object.assign({}, state, {count: state.count + number})
}

then you can call the corresponding version of action on the store this way

store.actions.inc(3)

getState(): state

Get current state directly. You should not modify the state it returns.

License

MIT