Persistent, cross-window state management with disk storage for Tauri desktop applications.
tauri-store is a state management library for Tauri desktop applications that provides persistent storage and synchronization capabilities. It allows developers to save application state to disk and keep it consistent across multiple windows, solving the problem of data loss when users close or restart desktop apps.
Tauri developers building desktop applications who need reliable state persistence and cross-window state synchronization without implementing custom storage solutions.
Developers choose tauri-store for its simple API, framework-agnostic core with dedicated plugins for popular libraries, and seamless integration with Tauri's architecture—offering persistent storage that feels native to desktop development.
Persistent stores for Tauri
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically saves state to the filesystem with methods like save(), ensuring data survives app restarts without manual intervention.
Keeps state consistent across all application windows in real-time, addressing a common pain point in multi-window desktop apps.
Offers dedicated plugins for Pinia, Valtio, Zustand, Vue, and Svelte, simplifying adoption in projects using these popular libraries.
Allows reading and writing from both JavaScript and Rust, leveraging Tauri's architecture for seamless backend-frontend communication.
Supports debouncing or throttling of store updates to reduce disk I/O and improve performance, as highlighted in the features.
Not an official Tauri plugin, which may result in slower updates, less community support, and potential breaking changes with Tauri releases.
The save() method is asynchronous while get/set are synchronous, creating a consistency hurdle that requires careful error handling to avoid race conditions.
Requires installing separate plugins for framework integration, adding configuration steps compared to using built-in state management solutions.
Documentation is hosted externally and may lack comprehensive examples or troubleshooting guides, posing a learning curve for complex use cases.