Store Refactorer

To refactor a large Zustand store, you break down monolithic files exceeding 300 lines into modular slices of 120 lines or less. This process extracts distinct state domains into separate slices while maintaining a combined store for persistence.

A god store is a large, monolithic state management file that becomes difficult to maintain and scale. You should split it when the file exceeds 300 lines, refactoring it into focused slices to improve code modularization and performance.

Yes, you can split a Zustand store without breaking backward compatibility by using facade exports. This ensures existing codebases remain functional while the internal state management is restructured into individual slices.

Implementing Zustand v5 best practices involves using individual selectors and applying persistence on the combined store. When extracting state slices, you can also configure selective persistence via Dexie to optimize local storage.

The best way to eliminate circular dependencies in a Zustand store is by consolidating duplicate stores and splitting god classes into modular slices. This refactoring isolates state logic, preventing the interlocking imports that cause circular dependencies.

Yes, Store Refactorer handles selective persistence with Dexie for Zustand slices. It configures persistence on the combined store while providing options to selectively persist specific slices, optimizing storage in large applications.