Zustand middleware composition order affecting persistence serialization

Middleware Composition Order and Serialization Behavior

Zustand's middleware system allows developers to compose multiple extensions like persist, serialize, and devtools. The order in which these middlewares are applied can significantly impact how state is transformed and stored. When using persist middleware with custom serialization options, the interaction between the middleware chain and the resulting stored data becomes critical.

The persist middleware handles writing state to storage, while serialize middleware controls how state is transformed before storage and restored after retrieval. If these are composed in different orders, the serialization may occur at different stages of the persistence pipeline, potentially leading to unexpected stored values or restoration behavior.

Documentation shows both persist and serialize as separate capabilities, but the exact interaction when both are applied to the same store shape requires clarification. The question is whether the serialize middleware wraps the persist middleware's internal operations or operates independently within the composition chain.

Specific Questions

• How does the composition order of persist and serialize middleware affect the data written to and restored from storage?
• Does the serialize middleware transform the state before persist writes it, or after persist retrieves it?
• What are the documented guarantees around middleware execution order in the official API reference?