Skip to content
Back to Stack Recommender

XState SPA

React + XState for statechart-driven SPAs.

FrontendComplex

Stack Components

FrameworkReact 19
StateXState 5
BuildVite 6
StylingTailwindCSS 4

Why

Formal state machines, visual debugging, SCXML compatible. JavaScript is used by 62% of developers per the Stack Overflow 2024 survey, and React holds 40% framework market share (State of JS 2024).

Vite replaced Webpack as the default bundler, cutting dev server startup from 30s to <1s.

When

Use for complex multi-step flows. Avoid for trivial state (overkill).

How

1. npm i xstate @xstate/react 2. Define machine with setup().createMachine() 3. Use useMachine hook in components

Example

const machine = setup({}).createMachine({ initial: 'idle', states: { idle: { on: { START: 'running' } }, running: { on: { STOP: 'idle' } } }, })

Common Problems

  • ⚠Machine complexity — split into hierarchical states
  • ⚠Actor communication — use spawn for child machines
  • ⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

  • ✓Use Stately visual editor for design
  • ✓Prefer useMachineSelector for performance
  • ✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is XState SPA and what projects is it for?

React + XState for statechart-driven SPAs. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with XState SPA in 10 minutes?

Two steps: (1) npm i xstate @xstate/react; (2) Define machine with setup().createMachine(). Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with XState SPA and how do I avoid it?

The most common pitfall is: Machine complexity — split into hierarchical states. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for XState SPA?

Best practices for XState SPA include: Use Stately visual editor for design; Prefer useMachineSelector for performance; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use Stately visual editor for design" — should be set up at project init to avoid costly rework later.

When should I NOT choose XState SPA?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). XState SPA shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.