SSR Example (SSR data is shared)

I’m using Next.js and have a separate file state.js that has something like this:

export const useSessionStore = create(combine({
  session: {},
}, set => ({
  setSession: (session) => set({ session }),
})))

And then calling setSession() on the server (for example in _app.js) after a successful login. When reading session on the server + client, it seems to work fine. So far so good.

The problem is: the session seems to be saved in Node.js memory and shared with everyone(?). When you login on one browser, the same session data is returned when you load the page on another browser. So I’m assuming when I set session on the server, it persists on Node.js side and returns the same session for all clients.

What am I doing wrong, or is zustand not meant for this?

[dai-shi]

v4 has new APIs for context use case. It would be nice to update the example. typing with middleware is improved in v4 too.

[kirill-konshin]

next-redux-wrapper does lots of things behind the scenes. It wraps Next.js hook methods and properly hydrates the state between client and server in various navigation scenarios and hook combinations. Unfortunately, I’m not familiar with Zustand, so I doubt I can help here.