Type does not flow properly when using the set during creation

[jsgoupil]

Bug Description

With the following code:

import { create } from 'zustand';

const initialState = { b: true};
const working = create(() =>initialState);
const notWorking = create(set => initialState);
const workaround = create<typeof initialState>(set => initialState);

The create with the set present will make the StoreApi have an unknown as the model.

The workaround only works if my initialState does not employ set.
Otherwise, I have to duplicate everything like:

const workaround2 = create<{ z: boolean }>(set => ({ z: true }));

Which becomes very cumbersome.

Even if this is the "norm", is there a better workaround?

TypeScript:
5.2.2

Reproduction Link

pasted

[dbritto-dev]

Bug Description

With the following code:

import { create } from 'zustand';

const initialState = { b: true};
const working = create(() =>initialState);
const notWorking = create(set => initialState);
const workaround = create<typeof initialState>(set => initialState);

The create with the set present will make the StoreApi have an unknown as the model.

The workaround only works if my initialState does not employ set. Otherwise, I have to duplicate everything like:

const workaround2 = create<{ z: boolean }>(set => ({ z: true }));

Which becomes very cumbersome.

Even if this is the "norm", is there a better workaround?

TypeScript: 5.2.2

Reproduction Link

pasted

JS middleware and TS -> create()(...)
JS no middleware or combine -> create(...)

[jsgoupil]

This doesn't work. It results to the same problem.

[dbritto-dev]

BTW, you don't need to explicitly type your store, you can use combine middleware to get fully inferred types ->

create(
  combine({ count: 0 }, (set) => ({
    increment: () => {
      set((state) => ({ count: state.count + 1 }));
    },
  })),
);

[jsgoupil]

I guess that's an option that I could look into. Thanks.

[dbritto-dev]

@jsgoupil on zustand you need to explicitly type your store if you are not using combine middleware