Simple and powerful state management for React and Inferno

  • laco

Downloads in past


1.2.15 years ago8 years agoMinified + gzip package size for laco in KB


npm version travis
Very simple and powerful state management solution for React and Inferno.
Set up your stores and subscribe to them. Easy as that!
Check out the introductory blog post.
npm install laco
npm install laco-inferno or npm install laco-react


  • :rocket: Simple to use
  • :tada: Lightweight (under 1kb in size)
  • :sparkles: Partial Redux DevTools Extension support (time travel)


import { Store } from 'laco'
import { Subscribe } from 'laco-react' // or 'laco-inferno'

// Creating a new store with an initial state { count: 0 }
const CounterStore = new Store({ count: 0 })

// Implementing some actions to update the store
const increment = () => CounterStore.set((state) => ({ count: state.count + 1 }))
const decrement = () => CounterStore.set((state) => ({ count: state.count - 1 }))

const Counter = () => (
  <Subscribe to={[CounterStore]}>
    {(state) => (
        <button onClick={decrement}>-</button>
        <button onClick={increment}>+</button>

For more examples check the examples folder.
Following commands are available for each example project:
npm run start:dev
npm run start:prod
npm run test

Redux DevTools Extension

Check out Redux DevTools Extension.

Time travel

Just click on the stopwatch icon and you will get a slider which you can play with. That's it! :)

React Native Debugger

Check out React Native Debugger.

Time travel

Works as you would expect :)!


Store(initialState: Object, name?: String)

// Initializing a new store with an initial state and a name:
const NewStore = Store({ count: 0 }, "Counter")
The name is optional and is used to get an overview of action and store relationship in Redux DevTools Extension. Action names for the Store will now show up as Counter - ${actionType} in DevTools Extension where as before only ${actionType} was shown.


// Getting the state of the store
Returns an object which could be something like { count: 0 } following the example.

Store.set(state: Function, info?: String)

// Setting a new state and passing an optional action name "increment"
Store.set((state) => { count: state.count + 1 }, "increment")

Store.replace(state: Function, info?: String)

Immutability is taking care of to a certain extent behind the scenes with the spread operator with Store.set() but you might want more control over the state. You can do this by using Store.replace() like so:
// Setting a new state and passing an optional action name "increment"
Store.replace((state) => { /* return modified state */}, "increment")

Store.setCondition(condition: Function)

// Setting a condition to prevent count from going below 0
// and a special case for `SudoDecrement` action which CAN make count go below 0
CounterStore.setCondition((state, actiontype) => {
  if (state.count >= 0) {
    return state
  } else if (actionType === 'SudoDecrement') {
    return state
  // Otherwise return nothing which does NOT change any state
Setting a condition on a store will make every Store.set() call go through the condition first.


// Resets the store to initial state
A good practice when testing is to call reset() on a store before using the store in a test. This takes care of some edge cases that you might run into. The reason for this is that Laco is using a global object behind the scenes to store all of your stores states into one big object. Redux also operates on one global object which makes time travel possible.

Store.dispatch(value: any, info: String)

// Dispatching an action that does not change the state of the store
Store.dispatch(changeLocation(), "Location change")
You might want to dispatch an action that is associated with a certain store but don't want to change the state. The action will in this case be shown as StoreName - Location change.

dispatch(value: any, info: String)

import { dispatch } from 'laco'

// Dispatching a global action that does not change any state
dispatch(changeLocation(), "Location change")
You might want to dispatch a global action that is NOT associated with any store. The action will in this case just be shown as Location change.

<Subscribe />


  • to - Array of stores you want to subscribe to
<Subscribe to={[CounterStore]}>
  {({ count }) => (
      <button onClick={decrement}>-</button>
      <button onClick={increment}>+</button>
The Subscribe component is making use of the new render prop idea. Related articles:


Testing using tape:
import * as test from 'tape'
import { CounterStore, increment, decrement } from './CounterStore'

test('counter', (t) => {
  t.assert(CounterStore.get().count === 0);

  t.assert(CounterStore.get().count === 1);

  t.assert(CounterStore.get().count === 0);



Heavily inspired by: