Basic xstate repo stats
12 days ago

davidkpiano/xstate is an open source project licensed under MIT License which is an OSI approved license.

Xstate Alternatives

Similar projects and alternatives to xstate

  • GitHub repo cra-template-redux

    The official Redux template for Create React App

  • GitHub repo fsl

    Finite State Language specification

  • GitHub repo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • GitHub repo create-react-app

    Set up a modern web app by running one command.

  • GitHub repo styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅

  • GitHub repo SWR

    React Hooks library for remote data fetching

  • GitHub repo downshift 🏎

    🏎 A set of primitives to build simple, flexible, WAI-ARIA compliant React autocomplete, combobox or select dropdown components.

  • GitHub repo headlessui

    Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.

  • GitHub repo zustand

    🐻 Bear necessities for state management in React

  • GitHub repo watchtower

    A process for automating Docker container base image updates.

  • GitHub repo proposal-pattern-matching

    Pattern matching syntax for ECMAScript

  • GitHub repo awesome-workflow-engines

    A curated list of awesome open source workflow engines

  • GitHub repo react-html-parser

    Converts HTML strings directly into React components and provide a simple way to modify and replace the content.

  • GitHub repo jssm

    Fast, easy Javascript finite state machines with visualizations; enjoy a one liner FSM instead of pages. MIT; Typescripted; 100% test coverage. Implements the FSL language.

  • GitHub repo jssm-viz

    Visualization of JSSM machines using viz.js

  • GitHub repo GolfPool

  • GitHub repo react-storybook

  • GitHub repo task-api

  • GitHub repo badcaller

    A Raspberry Pi-enabled caller ID system which checks incoming landline calls against databases of known malicious callers, and displays a danger rating of the incomming caller on a web interface.

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better xstate alternative or higher similarity.


Posts where xstate has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-04-29.
  • Scam protection using a Raspberry Pi to perform caller ID and risk-assess incoming calls | 2021-04-29
    Modems are FSMs, so I required no cajoling to give XState a try as I've had my eye on it for a while and I'm only slightly familiar with Machina. Check out the amazing, interactive visualisations you can do with XState.
  • Beginner's Thread / Easy Questions (April 2021) | 2021-04-02
    Not sure if this would count, but you can check out XState to manage complex states, though for simple ones, you can use reducers.
  • FSL: A programming language to make complex finite state machines easy to create | 2021-03-25
  • Bringing Pattern Matching to TypeScript 🎨 Introducing TS-Pattern v3.0 | 2021-03-15
    It’s not only the user interface, state management libraries as well have been taking a declarative turn. Libraries such as XState, Redux, and many more let you declaratively manage your application state to unlock the same benefits: writing code that is easier to understand, modify and test. Today, we truly live in a declarative programming world!
  • JavaScript/TypeScript finite state machines and statecharts for the modern web | 2021-03-05
  • OkCupid Presents: Modeling UI States in A React Form Component Using A Finite State Machine
    I've been using xstate a lot for this.
  • XState – State machines and statecharts for the modern web | 2021-03-02
  • Let's reason about state management (e.g. Redux, Apollo) in web apps | 2021-02-25
    Have you tried XState yet? I haven't reached the clientside of the system I'm building but I'm probably going to roll with it.
  • Boost your React application’s performance by Xstate | 2021-02-24
    Behind the state management Xstate gives you powerful control on the flow and different states. If you’re not familiar with the Xstate first take a look at the documents since this post is not about learning Xstate it’s about using it.
  • Rsvp to weddings with XState | 2021-02-19
    In this walkthrough, I'll solve those complexities and more with an XState machine.
  • Экосистема React в 2021 году | 2021-01-25
    XState - это библиотека для создания стейт машин, которые отлично подходят для представления сложной логики. На самом деле, они неплохо подходят и для несложной логики. В следующий раз, когда вы обнаружите, что жонглируете кучей логических значений или пытаетесь обновить кучу переменных в нужных местах, обратите внимание на XState. У есть хороший курс по XState от Kyle Shevlin.
  • You don't need a library for state machines | 2021-01-20
    So if we can get our basic state management needs met with a small, declarative, library-free state machine implementation (either using switch statements or objects), why do we need libraries such as XState?
  • How to do decision/confirmation modals and promises? | 2021-01-17
    My "weapon of choice" here is XState. It supports Actor Model (that message based communication I described) out of the box. It also have awesome visualizer and powerful inspector (to trace how your machines work in runtime and communicate), but it could be hard to grasp some concepts. And there is very welcoming and helpful community on spectrum and github, in case you will have any questions.
  • Recently picked up React JS (with hooks) and just learned plain Redux. Is vanilla Redux industry standard? Is there a better way to manage state with hooks and Redux? | 2021-01-12
  • State machines are wonderful tools | 2021-01-01
    This is only true when considering a specific software design that implements the state machine. I'd say the most popular way to define a state machine in code is how Xstate does it: You define your states, and then you define your inputs, and then you map out every single transition between states.

    This is probably the most inefficient way to design a state machine. There's a simple mathematical explanation for that. If we agree that a state diagram is a directed graph consisting of N nodes, then there are N^2 possible transitions (that's the definition of a completely connected graph). This means there's a large space of possible transitions relative to the number of states, which means there's a high probability that you will have to modify lots of transitions when modifying the state machine itself.

    In this article, this author is sharing several alternative designs for state machines, which don't look like they suffer from exactly the same problem. I'm most familiar with TLA+, where you describe a state machine simply with one logical predicate: the "Next" state relation. This is the most powerful way I've found to define state machines, and modifying one function to entirely change the behavior of the state machine is very easy in practice.