JavaScript Intellisense Issues

[TurtIeSocks]

Follow up from #262 (comment)

I have an older project I wrote in JS and is just a little too tedious to port entirely to TS, and I noticed that the intellisense doesn't seem to work when set and get (or only set) arguments are used when creating the store.

For example:
Creating this store:

Results in this intellisense:

But creating this store:

Results in no intellisense:

The results are the same for each scenario when wrapping the store with the persist middleware.

Version:
"zustand": "^4.3.9"

Zustand is imported like so (if it's helpful to know)

import { create } from 'zustand'
import { persist } from 'zustand/middleware'

Any suggestions?

Thank you for this wonderful lib! 🙏

[dai-shi]

Thanks for opening up a discussion.
I hope someone can dig into it.

Just out of curiosity, does changing create(...) to create()(...) change anything?

[TurtIeSocks]

It doesn't, unfortunately. It also caused the loss of intellisense in the scenario where set and get args aren't provided.

[prenaissance]

export type StateCreator<
  T,
  Mis extends [StoreMutatorIdentifier, unknown][] = [],
  Mos extends [StoreMutatorIdentifier, unknown][] = [],
  U = T,
> = ((
  setState: Get<Mutate<StoreApi<T>, Mis>, 'setState', never>,
  getState: Get<Mutate<StoreApi<T>, Mis>, 'getState', never>,
  store: Mutate<StoreApi<T>, Mis>
) => U) & { $$storeMutators?: Mos }

I think it boils down to the circular dependency between the initialization parameters and the T generic, making inference impossible. I tried rolling back Typescript's language server and the same result was replicated.

[prenaissance]

Here's quite a verbose solution using JSDoc.

[TurtIeSocks]

Thanks for this :) about the same as TS anyway (unless I've been using it wrong) and definitely better than nothing.