Update zustand 4.5.2 → 5.0.2 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ zustand (4.5.2 → 5.0.2) · Repo

Release Notes

5.0.2

This fixes some issues in middleware.

What's Changed

• fix(middleware): devtools type error #2700 by @AndyRightNow in #2875
• fix(persist): fix async migrate on persist middleware by @dbritto-dev in #2877

New Contributors

• @ennjin made their first contribution in #2834
• @ytraddan made their first contribution in #2836
• @m1nsuplee made their first contribution in #2847
• @gonzalezfj made their first contribution in #2861
• @mordv made their first contribution in #2869
• @marcoamt made their first contribution in #2874
• @AndyRightNow made their first contribution in #2875

Full Changelog: v5.0.1...v5.0.2

5.0.1

This fixes shallow function for some edge cases.

What's Changed

• fix(shallow): fallback map-like iterator comparison by @dai-shi in #2795
• fix(shallow): iterable-like insensitive keys order comparison (alternate implementation) by @dai-shi in #2821

New Contributors

• @legcy143 made their first contribution in #2799
• @kretajak made their first contribution in #2822
• @steaks made their first contribution in #2824

Full Changelog: v5.0.0...v5.0.1

5.0.0

🎉🎉🎉 Zustand v5 🐻🐻🐻

TL;DR

• No new features
• Drop many old things
• Migration from v4 should be smooth.

Changes in v5

• Drop default exports
• Drop deprecated features
• Make React 18 the minimum required version
• Make use-sync-external-store a peer dependency (required for createWithEqualityFn and useStoreWithEqualityFn in zustand/traditional)
• Make TypeScript 4.5 the minimum required version
• Drop UMD/SystemJS support
• Organize entry points in the package.json
• Drop ES5 support
• Stricter types when setState's replace flag is set
• Persist middleware behavioral change
• Other small improvements (technically breaking changes)

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:

Uncaught Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

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

• v5 by @dai-shi in #2138
• Fix Immer type inference for setState by @chrisvander in #2696

New Contributors

• @abernier made their first contribution in #2674
• @tthallos made their first contribution in #2501
• @sagiereder made their first contribution in #2673
• @melutovich made their first contribution in #2692
• @rgksugan made their first contribution in #2695
• @Anuovec made their first contribution in #2708
• @EthanRBrown made their first contribution in #2717
• @mym0404 made their first contribution in #2730
• @87xie made their first contribution in #2745
• @f312213213 made their first contribution in #2761
• @DanThemes made their first contribution in #2764
• @chaficnajjar made their first contribution in #2770
• @goosewobbler made their first contribution in #2781
• @Amyssyko made their first contribution in #2784
• @MartinGamesCZ made their first contribution in #2785

Full Changelog: v4.5.5...v5.0.0

4.5.5

This improves the persist middleware behavior for an edge case.

What's Changed

• fix(storage): avoid calling setItem with the state just retrieved by @double-thinker in #2678
• chore(deps): update dependencies by @dai-shi in #2680

New Contributors

• @alwalxed made their first contribution in #2634
• @YashChauhan858 made their first contribution in #2636
• @donutcube made their first contribution in #2650
• @vorant94 made their first contribution in #2661
• @jeppester made their first contribution in #2667
• @ryota-murakami made their first contribution in #2668
• @double-thinker made their first contribution in #2678

Full Changelog: v4.5.4...v4.5.5

4.5.4

There was an issue in v4.5.3 with some bundlers.

What's Changed

• fix: no type field in package.json by @dai-shi in #2622

Full Changelog: v4.5.3...v4.5.4

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment	0	11.5 kB	knownasilya
npm/[email protected]	None	0	88.8 kB	daishi, drcmda, jeremyrh

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎