tanstack-store

To manage shared UI state without unnecessary re-renders, use an immutable reactive store with selector-based subscriptions and shallow equality checks. This approach batches multiple updates into a single notification, ensuring components only re-render when their selected state slice actually changes.

The best way to compute derived state is using a Derived computed value that composes data from multiple stores. This method supports mountable lifecycle and previous-value awareness, allowing you to chain operations like filtering, sorting, and pagination predictably.

You can handle side effects and batch state updates by using Effect and batch operations. Effects manage side-effect logic tied to store dependencies, while batching groups multiple state updates into a single notification to avoid redundant renders.

Yes, this reactive store works with front-end frameworks including React, Vue, Solid, Angular, and Svelte. It provides a core immutable state container and offers a specific React adapter with a useStore hook for seamless integration.

Use an immutable reactive store instead of component-level state when managing shared application state across multiple components. It solves subscription cleanup issues and provides a single source of truth, whereas component state is better for localized, isolated data.