onNodesChange usage help

[Defite]

Hi everyone! I'm testing strange behaviour in my code with react version of xyflow.

I test dragging perfomance on 100 simple nodes withoud connected edges (arrows). When I use

const [nodes, setNodes, onNodesChange] = useNodesState(initialNodes);

everything is smooth both with devtools opened and closed.

When I use function from my custom Zustand store with this function

onNodesChange: (changes) => {
    set({
      nodes: applyNodeChanges(changes, get().nodes),
    });
  },

dragging becomes laggy (with drops to 2fps and freezes).

My store consists of slices and uses some middlewares like zundo and immer:

export const useEditorStore = create<AppStoreSlices>()(
  temporal(
    immer(
      devtools((...a) => ({
        ...editorSlice(...a),
        ...panelsSlice(...a),
        ...nodeSettingsSlice(...a),
        ...editorControlsSlice(...a),
      }))
    ),
    {
      partialize: (state) => {
        const { nodes, edges } = state;

        return { nodes, edges };
      },
      equality: (pastState, currentState) => {
        const remapNodes = (nodes: Node[]) => {
          return nodes.map(({ measured, dragging, ...node }) => ({
            ...node,
          }));
        };

        return deepEqual(
          { nodes: remapNodes(pastState.nodes), edges: pastState.edges },
          { nodes: remapNodes(currentState.nodes), edges: currentState.edges }
        );
      },
      limit: 50,
    }
  )
);

I tried comment them and use store without them - nothing changed.

I've attached editorSlice as it is too big to show here), but here is the onNodesChange function.

export const editorSlice: StateCreator<
  AppStoreSlices,
  [['zustand/immer', never], ['zustand/devtools', never]],
  [],
  EditorSliceState
> = (set, get) => ({
  nodes: [],
  onNodesChange: (changes) => {
      set({
        nodes: applyNodeChanges(changes, get().nodes),
      });
    },
    ...
});

Why it could possibly so dramatically drop in perfomance?

[Defite]

xyflow-zustand-repro-github.zip
I've attached code for reproducing this strange behaviour. My motivation to use zustand is because I'm using undo/redo with it and store some data there. I can rewrite my code to use redo/undo without making use of zustand, but it's rather strange behavior.