Relax types for persist middleware

[rafaeelaudibert]

Right now, we're requiring new StateStorage implementations to forcefully return void from inside setItem and removeItem.

When using a library that returns the set value for setItem or removeItem, therefore returning a string, it causes Typescript to fail, requiring some weird workarounds.

For example, when using localforage (https://github.com/localForage/localForage) one needs to do what we describe below. Notice the void keyword.

const storage: StateStorage = {
   ...localForage,
   setItem: void localForage.setItem.bind(localForage)
}

Another, longer, alternative is

const storage: StateStorage = {
   ...localForage,
   // Curly braces are required because we need to "return `void`"
   setItem: (name, value) => {
       localStorage.setItem(name, value)
  }
}

By changing the type implementation to ignore types - using unknown - we can simply use localforage - and similar libraries - as if we were using window.localStorage

Check List

• yarn run prettier for formatting code and docs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
zustand-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 14, 2024 2:55am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[dai-shi]

The change looks okay to me.

Does anyone want to give another review?

[dbritto-dev]

LGTM

[gideonkipkorir123]

This expression is not callable.
Type 'StoreApi' has no call signatures.