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

fatalist

v2.0.0

Published

Simple state manager based on state machines

Downloads

21

Readme

npm version Build Status PRs Welcome

Another one js state management library based on state machines.

Simple example

Let's say we have a button and we want to fetch some data, when clicking on it.

Simple markup:

<body>
    <button></button>
    <span></span>

    <script src="dist/main.js"></script>
</body>

Find our button and span in DOM.

import StateMachine, { bindMappings } from 'fatalist'

const button = document.querySelector('button')
const span = document.querySelector('span')

Then create our state machine with some initial state

const stater = new StateMachine('IDLE_STATE')

Then we're going to describe our machine states and transitions between them.

To do that we'll use addState and addTransition methods.

addState takes just a name of addable state.

addTransition takes three arguments: from, to and action. First two are pretty obvious. Third one is some king of action, which should be fired to perform a transition.

Notice, that if we want to reload data, we will make a transition from LOADED_STATE to LOADING_STATE.

stater.addState('IDLE_STATE')
stater.addState('LOADING_STATE')
stater.addState('LOADED_STATE')
stater.addTransition('IDLE_STATE', 'LOADING_STATE', 'load')
stater.addTransition('LOADING_STATE', 'LOADED_STATE', 'loaded')
stater.addTransition('LOADED_STATE', 'LOADING_STATE', 'load')

Of course we want to react on state changing in some way. So let's change the text inside button. We'll make it in a declarative way, by mapping texts to states.

const buttonTextMappings = {
    IDLE_STATE: 'Load stuff',
    LOADING_STATE: 'Loading stuff...',
    LOADED_STATE: 'Here u go',
}

There's a helper, called bindMappings. We will use it to map current state to text, which we want to see inside button, and in case, when we did not describe some case inside our mappings object, we'll fallback to default value.

const getButtonText = bindMappings(buttonTextMappings).withDefault('Load stuff')

Subscribe on state changing.

stater.subscribe(state => {
    button.textContent = getButtonText(state)
})

You may be wondering, how will we handle side effects? There's a trigger mechanism in Fatalist. It's kinda similar to commands in Elm. We are reacting on some event by putting a trigger on it. It will be fired on a state change.

const onLoadTrigger = (currentState, dispatch) =>
    fetch('https://jsonplaceholder.typicode.com/todos/1')
        .then(response => response.json())
        .then(data => span.textContent = data.title)
        .then(_ => stateMachine.dispatch('loaded'))

stater.setTrigger('load', onLoadTrigger)

Put click listener on our button.

button.addEventListener('click', () => stater.dispatch('load'))