xstate VS jssm

XState is a powerful library with comprehensive documentation. Keeping the documentation handy while building your next app with XState will be invaluable.

XState is an excellent library that simplifies the utilization of actors in JavaScript applications. While this article focuses on using React, these principles apply equally well to other frameworks. In fact, they can be implemented anywhere JavaScript is executed.

In this article, I want to share a personal journey of discovery in the world of state management. My path led me to XState, a tool that I believe is the best choice for managing state in modern applications like React, Angular, Vue, and others. This isn't just a professional advice; it's a personal recommendation based on real-world experience.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Lastly, I know that I've omitted many great tools like XState, React Query, and SWR. These tools are utilities that are very scalable in their own right, but aren't full replacements for a good state manager.

https://github.com/StoneCypher/jssm

I find the DSL much easier to wrap my head around than the json format of Xstate.

By example, my hobby library JSSM has currently 4904 unit tests that get run in 14 different contexts, and 1.3 million unicode tests that get run in eight contexts.

I use tsc to compile and rollup to bundle

Javascript State Machine

By the way, this is written in Typescript, and type protections are used extensively.

Here's the test directory for one of my things.

This is my general approach