State management

Persistent immutable data structures for JavaScript.

Good for

Managing complex collections while retaining previous versions of state.

Atomic state management for React.

Good for

Composing shared state from small independently managed atoms.

Observable state management with automatic dependency tracking.

Good for

Deriving reactive UI updates from mutable application models.

A state container combining typed models with observable state.

Good for

Structuring application state around models, actions, and snapshots.

Small reactive stores that work across several UI frameworks.

Good for

Sharing focused pieces of state without a large state-management setup.

Type-safe state management stored in URL search parameters.

Good for

Keeping filters, pagination, and shareable view state in the address bar.

An atom-and-selector state-management library originally developed for React.

Good for

Understanding or maintaining applications that already use Recoil.

The recommended tooling for writing Redux state logic.

Good for

Managing shared state with predictable actions, reducers, and debugging support.

A reactive data store designed for local-first applications.

Good for

Managing structured client data with reactive views and persistence.

Proxy-based state management for React and JavaScript.

Good for

Writing mutable-looking state updates with reactive snapshots for rendering.

A lightweight state store based on events and explicit transitions.

Good for

Managing local or shared state with clearly defined update events.

A small state-management library with hook-based access.

Good for

Sharing application state through a straightforward external store.