feat: migrate from Easy Peasy to Zustand for state management (fixes settings and onboarding) #1866
+1,342
−1,023
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
name: pull request
about: submit changes to the project
title: "[pr] Replace Easy Peasy with Zustand for improved performance and SSR"
labels: ''
assignees: ''
description
Replace Easy Peasy state management with Zustand across the entire application to improve performance, resolve SSR hydration issues, and enhance type safety. This migration was triggered by critical issues: the settings dialogue not working properly, onboarding always showing, and analytics remaining active despite being disabled.
Key Changes:
State Management Migration
Cross-Platform Improvements
getDataDir()
using Tauri'sappDataDir()
Authentication & User Management
Performance & Reliability
UI/UX Enhancements
Technical Debt Resolution
SSR & Hydration Fixes
Implementation Notes: Vibe coded with Claude Code while trying to maintain a clean, organised code structure. Extensive manual testing was performed to ensure reliability.
related issue: #
how to test
Files Changed: 48 files, 1,342 insertions, 1,023 deletions
Breaking Changes: None - maintains full backwards compatibility
Screenshots showing working settings persistence, single onboarding display, and clean console logs (no hydration errors) would help verify that the core issues are resolved.
if you are not the author of this PR and you see it and you think it can take more than 30 mins for maintainers to review, we will tip you between $20 and $200 for you to review and test it for us.