Unexpected re-render when zustand selector returns fresh object reference
The goal is to adopt zustand feature by feature in a small React app while legacy Redux or context state remains in place, without causing avoidable re-renders during the migration. Zustand compares the result of each useStore selector with Object.is by default. If a selector returns a new object or array reference on every evaluation, components can re-rend