xstate-tree

xstate-tree was born as an answer to the question "What would a UI framework that uses Actors as the building block look like?". Inspired by Thomas Weber's Master Thesis on the topic. XState was chosen to power the actors with React powering the UI derived from the actors.

xstate-tree was designed to enable modeling large applications as a single tree of xstate machines, with each machine being responsible for smaller and smaller sub sections of the UI. This allows modeling the entire UI structure in state machines, but without having to worry about the complexity of managing the state of the entire application in a single large machine.

Each machine has an associated, but loosely coupled, React view associated with it. The loose coupling allows the view to have no knowledge of the state machine for ease of testing and re-use in tools like Storybook. Actors views are composed together via "slots", which can be rendered in the view to provide child actors a place to render their views in the parent's view.

While xstate-tree manages your application state, it does not have a mechanism for providing global application state accessible by multiple actors, this must be provided with another library like Redux or GraphQL. It does provide a routing solution, outlined here.

At Koordinates we use xstate-tree for all new UI development. Our desktop application, built on top of Kart our Geospatial version control system, is built entirely with xstate-tree using GraphQL for global state.

A minimal example of a single machine tree:

1import React from "react";
2import { createRoot } from "react-dom/client";
3import { setup, assign, assertEvent } from "xstate";
4import {
5  createXStateTreeMachine,
6  buildRootComponent
7} from "@koordinates/xstate-tree";
8
9type Events =
10  | { type: "SWITCH_CLICKED" }
11  | { type: "INCREMENT"; amount: number };
12type Context = { incremented: number };
13
14// A standard xstate v5 machine, nothing extra is needed for xstate-tree
15const machine = setup({
16  types: { context: {} as Context, events: {} as Events },
17  actions: {
18    increment: assign({
19      incremented: ({ context, event }) => {
20        assertEvent(event, "INCREMENT");
21        return context.incremented + event.amount;
22      }
23    })
24  }
25}).createMachine({
26  id: "root",
27  initial: "inactive",
28  context: {
29    incremented: 0
30  },
31  states: {
32    inactive: {
33      on: {
34        SWITCH_CLICKED: "active"
35      }
36    },
37    active: {
38      on: {
39        SWITCH_CLICKED: "inactive",
40        INCREMENT: { actions: "increment" }
41      }
42    }
43  }
44});
45
46const RootMachine = createXStateTreeMachine(machine, {
47  // Selectors to transform the machines state into a representation useful for the view
48  selectors({ ctx, canHandleEvent, inState }) {
49    return {
50      canIncrement: canHandleEvent({ type: "INCREMENT", amount: 1 }),
51      showSecret: ctx.incremented > 10,
52      count: ctx.incremented,
53      active: inState("active")
54    }
55  },
56  // Actions to abstract away the details of sending events to the machine
57  actions({ send, selectors }) {
58    return {
59      increment(amount: number) {
60        send({
61          type: "INCREMENT",
62          amount: selectors.count > 4 ? amount * 2 : amount
63        });
64      },
65      switch() {
66        send({ type: "SWITCH_CLICKED" });
67      }
68    }
69  },
70
71  // If this tree had more than a single machine the slots to render child machines into would be defined here
72  // see the codesandbox example for an expanded demonstration that uses slots
73  slots: [],
74  // A React component view to bring it all together
75  // the return value is a plain React component that can be rendered anywhere by passing in the needed props
76  // the view has no knowledge of the machine it's bound to
77  View({ actions, selectors }) {
78    return (
79      <div>
80        <button onClick={() => actions.switch()}>
81          {selectors.active ? "Deactivate" : "Activate"}
82        </button>
83        <p>Count: {selectors.count}</p>
84        <button
85          onClick={() => actions.increment(1)}
86          disabled={!selectors.canIncrement}
87        >
88          Increment
89        </button>
90        {selectors.showSecret && <p>The secret password is hunter2</p>}
91      </div>
92    );
93  },
94});
95
96// Build the React host for the tree
97// You can pass input to the machine via the input prop
98const XstateTreeRoot = buildRootComponent(RootMachine);
99
100// Rendering it with React
101const ReactRoot = createRoot(document.getElementById("root"));
102ReactRoot.render(<XstateTreeRoot />);

A more complicated todomvc example

Overview

Each machine that forms the tree representing your UI has an associated set of selector, action, view functions, and "slots"

• Selector functions are provided with the current context of the machine, a function to determine if it can handle a given event and a function to determine if it is in a given state, and expose the returned result to the view.
• Action functions are provided with the send method bound to the machines interpreter and the result of calling the selector function
• Slots are how children of the machine are exposed to the view. They can be either single slot for a single actor, or multi slot for when you have a list of actors.
• View functions are React components provided with the output of the selector and action functions, and the currently active slots

API

To assist in making xstate-tree easy to use with TypeScript there is the createXStateTreeMachine function for typing selectors, actions and view arguments and stapling the resulting functions to the xstate machine

createXStateTreeMachine accepts the xstate machine as the first argument and takes an options argument with the following fields, it is important the fields are defined in this order or TypeScript will infer the wrong types:

• selectors, receives an object with ctx, inState, canHandleEvent, and meta fields. ctx is the machines current context, inState is the xstate state.matches function to allow determining if the machine is in a given state, and canHandleEvent accepts an event object and returns whether the machine will do anything in response to that event in it's current state. meta is the xstate state.meta object with all the per state meta flattened into an object
• actions, receives an object with send and selectors fields. send is the xstate send function bound to the machine, and selectors is the result of calling the selector function
• View, is a React component (note the capital V) that receives actions, selectors, and slots as props. actions and selectors being the result of the action/selector functions and slots being an object with keys as the slot names and the values the slots React component

Full API docs coming soon, see #20

Slots

Slots are how invoked/spawned children of the machine are supplied to the Machines view. The child machines get wrapped into a React component responsible for rendering the machine itself. Since the view is provided with these components it is responsible for determining where in the view output they show up. This leaves the view in complete control of where the child views are placed.

Slotted machines are determined based on the id of the invoked/spawned machine. There are two types of slots, single and multi. Single slots are for invoked machines, where there will only be a single machine per slot. Multi slots are for spawned machines where there are multiple children per slot, rendered as a group; think lists. There is a set of helper functions for creating slots which in turn can be used to get the id for the slot.

singleSlot accepts the name of the slot as the first argument and returns an object with a method getId() that returns the id of the slot.
multiSlot accepts the name of the slot and returns an object with a method getId(id: string) that returns the id of the slot

You should always use the getId methods when invoking/spawning something into a slot. Each slot the machine has must be represented by a call to singleSlot or multiSlot and stored into an array of slots. These slots must be passed to the createXStateTreeMachine function.

Inter-machine communication

Communicating between multiple independent xstate machines is done via the broadcast function. Any event broadcast via this function is sent to every machine that has the event in its nextEvents array, so it won't get sent to machines that have no handler for the event.

To get access to the type information for these events in a machine listening for it, use the PickEvent type to extract the events you are interested in

ie PickEvent<"FOO" | "BAR"> will return {type: "FOO" } | { type: "BAR" } which can be added to your machines event union.

To provide the type information on what events are available you add them to the global XstateTreeEvents interface. This is done using declare global

declare global {
  interface XstateTreeEvents {
    BASIC: string;
    WITH_PAYLOAD: { a: "payload" }
  }
}

That adds two events to the system, a no payload event ({ type: "BASIC" }) and event with payload ({ type: "WITH_PAYLOAD"; a: "payload" }). These events will now be visible in the typings for broadcast and PickEvent. The property name is the type of the event and the type of the property is the payload of the event. If the event has no payload, use string.

These events can be added anywhere, either next to a component for component specific events or in a module for events that are for multiple machines. One thing that it is important to keep in mind is that these declare global declarations must be loaded by the .d.ts files when importing the component, otherwise the events will be missing. Which means

1. If they are in their own file, say for a module level declaration, that file will need to be imported somewhere. Somewhere that using a component will trigger the import
2. If they are tied to a component they need to be in the index.ts file that imports the view/selectors/actions etc and calls createXStateTreeMachine. If they are in the file containing those functions the index.d.ts file will not end up importing them.

Utilities

viewToMachine

This utility accepts a React component and wraps it with an xstate-tree machine so you can easily invoke arbitrary React components in your xstate machines. This utility also accepts Root components returned from buildRootComponent.

1function MyView() {
2  return <div>{"My View"}</div>;
3}
4
5const MyViewMachine = viewToMachine(MyView);

buildRoutingMachine

This utility aims to reduce boilerplate by generating a common type of state machine, a routing machine. This is a machine that solely consists of routing events that transition to states that invoke xstate-tree machines.

The first argument is the array of routes you wish to handle, and the second is an object mapping from those event types to the xstate-tree machine that will be invoked for that routing event. The utility now supports routes with dots in their event names (e.g., "user.profile.view").

1const routeA = createRoute.simpleRoute()({
2  url: "/a",
3  event: "GO_TO_A",
4});
5const routeB = createRoute.simpleRoute()({
6  url: "/b",
7  event: "GO_TO_B",
8});
9
10const RoutingMachine = buildRoutingMachine([routeA, routeB], {
11  GO_TO_A: MachineA,
12  GO_TO_B: MachineB,
13});

Type helpers

There are some exported type helpers for use with xstate-tree

• SelectorsFrom<TMachine>: Takes a machine and returns the type of the selectors object
• ActionsFrom<TMachine>: Takes a machine and returns the type of the actions object
• AnyXstateTreeMachine: Type for any xstate-tree machine, useful for function parameters

New Features in v5

buildRootComponent Input Support

You can now pass input to your root machine when using buildRootComponent. The function signature has changed to accept a single object parameter:

1// Without routing
2const XstateTreeRoot = buildRootComponent(RootMachine);
3
4// With routing
5const XstateTreeRoot = buildRootComponent({
6  machine: RootMachine,
7  routing: {
8    routes,
9    history,
10    basePath: "/"
11  }
12});
13
14// Pass input to the machine
15ReactRoot.render(<XstateTreeRoot input={{ initialData: data }} />);

useOnRoute Hook

A new hook for executing side effects when specific routes are active. Unlike useIsRouteActive, this hook tells you when you're on the exact route (not just part of the active route chain):

1import { useOnRoute } from "@koordinates/xstate-tree";
2
3function MyComponent() {
4  useOnRoute(myRoute, ({ params, query }) => {
5    // Execute side effects when myRoute is the active end route
6    console.log("Route is active with params:", params);
7  });
8}

Children Support for Root Components

Root components and slots now support passing children, allowing you to wrap your application with providers:

1<XstateTreeRoot>
2  <GlobalProvider>
3    {/* Your app renders here */}
4  </GlobalProvider>
5</XstateTreeRoot>

Improved lazy Loading

The lazy utility now supports passing input to the lazily loaded machine:

1const LazyMachine = lazy(() => import("./MyMachine"), {
2  Loader: () => <div>Loading...</div>,
3  input: { initialData: "data" }
4});

Testing Improvements

• TestRoutingContext now supports nesting routing roots for better testing scenarios
• Removed deprecated testing utilities: buildTestRootComponent, buildViewProps, slotTestingDummyFactory

Logging Improvements

• Internal XState events are now filtered from logs for cleaner output
• _subscription property is stripped from logged data
• Route objects are no longer logged after matching to reduce console noise
• loggingMetaOptions export available for configuring logging behavior

Breaking Changes from v4

• Removed v1 style builders: buildView, buildSelectors, buildActions have been removed. Use createXStateTreeMachine instead.
• Child actor behavior: Children in final states are no longer automatically removed from views. You must manually call stopChild to remove them.
• Testing utilities removed: buildTestRootComponent, buildViewProps, and slotTestingDummyFactory have been removed.

Storybook

It is relatively simple to display xstate-tree views directly in Storybook. Since the views are plain React components that accept selectors/actions/slots as props you can just import the view and render it in a Story

There is a utility in xstate-tree to make this easier:

genericSlotsTestingDummy

This is a simple Proxy object that renders a