Update dependency zustand to v5 (main) #2635
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.
This PR contains the following updates:
^4.4.7
->^5.0.0
Release Notes
pmndrs/zustand (zustand)
v5.0.0
Compare Source
🎉🎉🎉 Zustand v5 🐻🐻🐻
TL;DR
Changes in v5
createWithEqualityFn
anduseStoreWithEqualityFn
inzustand/traditional
)Migration Guide
Read the migration guide carefully:
https://github.com/pmndrs/zustand/blob/main/docs/migrations/migrating-to-v5.md
Frequently Reported Issue
During the RC period, some users encountered the following infinite loop error:
This case was already a non-ideal behavior in v4 but appears more explicitly as an error in v5. While there are several ways to resolve this, using
useShallow
often fixes the problem.What's Changed
setState
by @chrisvander in https://github.com/pmndrs/zustand/pull/2696New Contributors
Full Changelog: pmndrs/zustand@v4.5.5...v5.0.0
Configuration
📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.