
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
A tiny state-management library with minimal API
npm install --save tiny-state
CommonJS
const createState = require('tiny-state');
ES6 modules (transpiled to CommonJS)
import createState from 'tiny-state';
Directly in browser (will be global createState variable)
<script src='/libs/tiny-state/index.js'></script>
var state = createState({
a: 100,
b: 200
});
If nothing is passed to createState, it will just be an empty object.
Once state is created, you can add subscribers to it:
var calculate = function(state) {
console.log(state.a + state.b);
}
state.subscribe(calculate);
Or, alternatively:
var SomeObject = {
c: 300,
// this will allow us to preserve `this` word;
// same will work with classes
handleUpdate: function(state) {
console.log(state.a + state.b + this.c);
}
};
state.subscribe(SomeObject); // once state changes, `SomeObject.handleUpdate` will be called
You can change state simply by calling state.change:
state.change(function(state) {
state.a = 400;
state.b = 500;
// or, change anything you want
});
This will trigger update of the subscribers, who are subscribed to state. So, both calculate and SomeObject.handleUpdate will be called after this.
If you don't want to trigger update of subscribers, you can just directly modify the state like so:
state.a = 400;
state.b = 500;
state.unsubscribe(calculate);
Or:
state.unsubscribe(SomeObject);
Treat each state as a subscription point. Parts of your app may want to subscribe to different parts of the state. So, there's no shame in nesting states like so:
var state = createState({
someGlobal: createState({ value: 100 })
});
Different parts of your app might want to create state for themselves, and subscribe to some parts of the global state. Take this React example:
// suppose this is some global in another file
state.c = createState({ value: 300 });
// and here's our React component
class MyApp extends React.Component {
componentWillMount() {
// creating own state
state.MyApp = createState({
a: 100,
b: 200
});
state.MyApp.subscribe(this); // subscribing to own state
state.c.subscribe(this); // subscribing to global state
}
// don't forget to unsubscribe before the component is discarded
componentWillUnmount() {
state.c.unsubscribe(this);
state.MyApp.unsubscribe(this);
delete state.MyApp; // no longer need to keep state.MyApp
}
// `handleUpdate` method for subscribing
handleUpdate() {
this.forceUpdate(); // This will trigger re-render
}
render() {
return (
<div>
<div>Calculated Result: { state.MyApp.a + state.MyApp.b + state.c.value }</div>
<button onClick={() => {
state.MyApp.change((MyApp) => {
MyApp.a += 100;
})
}}> Change state.MyApp.a </button>
</div>
)
}
}
Note that we use state.c.value. We can't just use state.c, because state.c is a state that has to be an object, so that we can store subscribers within it.
If you need to, you can also see who modified the state within handleUpdate:
handleUpdate(state) {
if(state === state.MyApp) {
console.log('state.MyApp changed, do one kind of update');
}
else if(state === state.c) {
console.log('state.c changed, do another kind of update');
}
}
FAQs
A tiny state-management library with minimal API
We found that tiny-state demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.