Zustand devtools regression with Redux Devtools 4 April 2025?

[holloway]

Bug Description

Redux Devtools Version 3.2.10 Released Apr 4, 2025 shows only 1 store (there are 3)...

see dropdown "18/3" which is the wrong name but at least is one

Whereas Version 3.1.6 Released Dec 15, 2023 shows 3 stores...

Installing @redux-devtools/extension per the docs doesn't seem to affect the behavior.

Trying to configure Zustand devtools() with {store: 'store 1'} or {name: 'store 1'} (unique for every store) doesn't seem to affect it either.

Reproduction Link

https://stackblitz.com/edit/vitejs-vite-bvylq4ez?file=package.json,src%2FApp.tsx

[dai-shi]

Thanks for reporting. Would anyone like to dig into it and find what caused it?

[kwonmoto]

I dug into this. It's not a zustand bug — it's a regression in the Redux DevTools extension's MV3 rewrite.

Since reduxjs/redux-devtools#1714 (extension 3.2.0, MV3) the panel can no longer read the background store directly. reduxjs/redux-devtools#1771 (3.2.7) added a state replay when the panel connects, but it replays only the most recently active instance, and without its name — which is exactly why you see a single store named like 18/3 (that's the internal tabId/instanceId). Extension 3.1.6 predates the MV3 rewrite, which is why it still works.

I reproduced this with a local build of the extension (3 zustand stores with devtools({ name }) → panel shows 1 instance named 920546649/1) and verified that replaying all instances with their stored names fixes it (all 3 stores appear with correct names).

Filed upstream: reduxjs/redux-devtools#2053, fix PR: reduxjs/redux-devtools#2054