jssm-viz VS jssm

Here's the rollup config for one of my libraries. This one has a common sense typescript and react setup, and produces three bundles, one each for iife, commonjs, and es6 module (each is the whole library, just meant for a different user use case)

JSSM has JSSM-viz.

https://github.com/StoneCypher/jssm-viz

If you just want one to use, rather than to embed in your own software, The thing everyone's calling a live editor is actually the JSSM-viz demo. You can use that

https://stonecypher.github.io/jssm-viz-demo/graph_explorer.h...

It's kept outside of the main repo because, like xstate's, it's built on a transcompile of graphviz called viz.js, which is made with emscripten

It's several meg, and not many people want visualization, so I keep them in separate packages

You can get the graphviz code by hitting "dot" at the top, if you want to customize in ways the language doesn't know

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