I solved it by using create instead of createStore, and passing that result to createTrackedSelector.

const store = create(
  persist(
    subscribeWithSelector(redux(reducer, initialState as TStateWithDispatch)),
    {
      name: "myApp",
      storage: createJSONStorage(() => AsyncStorage),
    }
  )
);

const useTrackedSelector = createTrackedSelector(store);

What this does:

export { default as createStore } from './vanilla'

is - it takes the default export from that file, and in this file, exports it under the name createStore.

What this does:

export { default } from './react'

is - it takes the default export from that file, and in this file, exports it as default.

Without lines 3 and 4, the above would not occur - neither default export from vanilla nor react would be re-exported here. (doing export * from only re-exports named exports)

create is not a named export in the vanilla nor react files, and neither lines 3 nor 4 create an export named create, so import { create } from 'zustand' (which tries to retrieve the export named create) isn't permitted.

When consuming zustand, to import vanilla's default export, you'd need to do

import { createStore } from 'zustand';
// this can be renamed when importing with `as` if desired

To import React's default export, you'd need to do

import create from 'zustand';
// this can be named whatever you want, since it's a default import

If lines 3 and 4 didn't exist, neither of those two above snippets would work, because the default exports from react and vanilla wouldn't be re-exported.

#1945 is open.

@pullmann4rent are you using typescript? In that case please follow our TypeScript guide

The point is you can create v3 compatible createContext with v4 new APIs.
We want to make the library minimalistic, and thus considering deprecation.

Your feedback is important and I agree that there are some use cases. I wonder if anyone would be interested in creating a 3rd-party package, if it's valuable.