* doc: Added zustand-interval-persist to third party
* doc: added zustand-interval-persist to third party in alphabetical order.
* doc: re-arranged zustand-interval-persist order, zundo and zukeeper
* update vitest
* use resolve
* patch for older ts
* for older ts
* hack with any
* for other builds
* wip: for umd
* Revert "wip: for umd"
This reverts commit a5c0d6beaa80cbbdcad7961b77d593effd6a83c8.
* wip: esm
* wip: system
* Revert "wip: system"
This reverts commit aa919631a94a5b321fa9f2ec6c26b826c37ca3b0.
* wip: umd
* wip: hack cjs
* system cannot be tested
* Update third-party-libraries.md
* docs: order davstack store link alphabetically
* docs: add link to 3rd party autogenerated selectors library
* Update docs/integrations/third-party-libraries.md
change the dash
Co-authored-by: Blazej Sewera <code@sewera.dev>
---------
Co-authored-by: Blazej Sewera <code@sewera.dev>
Corepack chooses package manager to use with the
field `packageManager`. For users using Yarn
through Corepack, this is a real convenience.
Co-authored-by: Daishi Kato <dai-shi@users.noreply.github.com>
* updated readme with more examples
* moved example to docs from readme
* formatted code with Prettier
---------
Co-authored-by: Ankit Sagar <ankit.sagar@telnesstech.com>
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.
```typescript
const storage: StateStorage = {
...localForage,
setItem: void localForage.setItem.bind(localForage)
}
```
Another, longer, alternative is
```typescript
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`