Update zustand 4.5.2 → 4.5.5 (patch) #3242
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ zustand (4.5.2 → 4.5.5) · Repo
Release Notes
4.5.5
4.5.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 42 commits:
4.5.5
chore(deps): update dependencies (#2680)
fix(storage): avoid calling setItem with the state just retrieved (#2678)
fix: "value" to "content" attr for og:image (#2668)
Fix store-persistence example (#2667)
remove unintended change from default merge behaviour to identical but manual one (#2661)
chore: enable verbatimModuleSyntax in tsconfig (#2649)
Update persisting-store-data.md (#2650)
update compressed-size-action.yml
ci: fix pnpm setup (#2628)
doc: Added zustand-interval-persist to third party (#2636)
🐛 FIX: Correct an outdated comparison between Jotai and Zustand (#2634)
4.5.4
fix: no type field in package.json (#2622)
4.5.3
chore(deps): update dev dependencies (#2620)
useStore uses ReadonlyStoreApi (#2586)
chore: discussion template
chore: add react compiler eslint rules (#2612)
chore: issue template
doc: added zustand-computed-state to external libraries (#2598)
doc: added treeshakable to external libraries (#2595)
update: example/demo (#2585)
chore(deps): update dev dependencies (#2582)
prefer npm-stat
chore: publish workflow (#2569)
chore(deps): update dev dependencies (#2565)
docs: add @prncss-xyz/zustand-optics to third party libraries (#2564)
Update typescript.md - middleware order (#2558)
docs: fix typos in the typescript guide (#2550)
Migrate to pnpm (#2545)
Fix type in nextjs.md (#2530)
docs: add zustand-context to third party libs (#2525)
docs: update ramda example (#2510)
docs: add zustand-slices (#2494)
Update guides (#2474)
chore: old ts versions to test in ci (#2469)
update vitest (#2462)
Update third-party-libraries.md (#2435)
Fixing typo in nextjs.md (#2416)
Create FUNDING.json
chore(tests): suppress expected warnings (#2398)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands