useStore stops firing on state changes after component remounts about zustand HOT 9 CLOSED

Downgrading to 2.2.1 seems to fix this issue. Tested by downgrading the zustand package in the above codesandbox.

from zustand.

Dug in a little and it seems that subscribers are indeed being overwritten like in #84, in this case the child gets assigned same index as its parent.

What about compressing the subscribers array right after adding a subscriber? This seems to solve this issue as well as work with #84, while keeping order/indices intact. E.g: Below does not work as is.

const subscribe: Subscribe<TState> = <StateSlice>(
    subscriber: Subscriber<TState, StateSlice>
  ) => {
    // ...
    subscribers[subscriber.index] = subscriber;

    subscriberCount = 0;
    subscribers = subscribers.filter(s => {
      subscriber.index = subscriberCount++;
      return true;
    });

    return () => delete subscribers[subscriber.index];
  };

from zustand.

I have the same problem

from zustand.

me too

from zustand.

me too! HELP ZUSTAND TEAM

from zustand.

Any news on this? Seems to still be a problem

from zustand.

@dentrado On version 2.2.1, everything is fine

from zustand.

But then I get the bug they fixed in 2.2.2 instead

from zustand.

@dentrado very sadly (

from zustand.