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

react-states-machine

v1.2.0

Published

React finite state machine done right

Downloads

10

Readme

React State Machine

Build Status NPM Downloads pledge

Architecture your React components the right way using a simple and elegant finite state machine.

Usage

import machine from 'react-states-machine'

// describe flow using state machine
function Flow () {
  return (
    <div>
      {machine({
        // welcome state
        'welcome': [
          props => <button onClick={() => props.transition('click')}>Welcome</button>,
          {
            // click transition
            'click': [
              () => ({message: 'Hello you!'}),
              'next'
            ]
          }
        ],
        // next state
        'next': [
          props => {
            return (
              <div>
                <button onClick={() => props.goto('welcome')}>previous</button>
                {props.message}
                <button onClick={() => props.transition('update')}>next</button>
              </div>
            )
          },
          {
            'update': [() => ({message: 'This is awesome!'})]
          }
        ]
      })}
    </div>
  )
}

React states machines works with react native, react dom and all environments using JSX.

Getting started

A state machine is an object describing your application/component states.

machine({
  state: [
    component,
    transitions
  ]
})

A state is composed of a component as well as an optional object containing transitions to mutate this component. Here's an example that shows how to style an input when empty using a transition called validity:

machine({
  'inputState': [
    props => <input className={props.invalid ? 'invalid' : ''} onChange={e => props.transition('validity', e.target.value)}/>,
    {
      'validity': [(prev, value) => {
        return {
          invalid: !value
        }
      }]
    }
  ]
})

A transition is a function used to pass props to your component and update it. A transition is also useful to describe the passage to an other state. Here's an example:

machine({
  'formEmail': [
    props => {
      return (
        <div>
          <input type="email" />
          <button onClick={() => props.transition('next')}>next</button>
        </div>
      )
    },
    {
      next: [() => ({name: 'John Doe'}), 'formPassword']
    }
  ],
  'formPassword': [
    props => {
      return (
        <div>
          <h2>Hello {props.name}</h2>
          <input type="password" />
          <button>connect</button>
        </div>
      )
    }
  ]
})

But you also can go to an other state without transition:

machine({
  'formEmail': [
    props => {
      return (
        <div>
          <input type="email" />
          <button onClick={() => props.goto('formPassword')}>next</button>
        </div>
      )
    }
  ],
  'formPassword': [
    props => {
      return (
        <div>
          <h2>Hello {props.name}</h2>
          <input type="password" />
          <button>connect</button>
        </div>
      )
    }
  ]
})

Check out our test suite for more information.

Installation

npm install react-states-machine --save

NPM

Question

For questions and feedback please use our twitter account. For support, bug reports and or feature requests please make sure to read our community guideline and use the issue list of this repo and make sure it's not present yet in our reporting checklist.

Contribution

Cookie-token is an open source project and would not exist without its community. If you want to participate please make sure to read our guideline before making a pull request. If you have any react-states-machine related project, component or other let everyone know in our wiki.

Licence

The MIT License (MIT)

Copyright (c) 2016 Olivier Wietrich

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.