chore(deps): update dependency zustand to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
zustand	^4 -> ^4 || ^5.0.0

---

Release Notes

pmndrs/zustand (zustand)

v5.0.1

Compare Source

This fixes shallow function for some edge cases.

What's Changed

• fix(shallow): fallback map-like iterator comparison by @​dai-shi in https://github.com/pmndrs/zustand/pull/2795
• fix(shallow): iterable-like insensitive keys order comparison (alternate implementation) by @​dai-shi in https://github.com/pmndrs/zustand/pull/2821

New Contributors

• @​legcy143 made their first contribution in https://github.com/pmndrs/zustand/pull/2799
• @​kretajak made their first contribution in https://github.com/pmndrs/zustand/pull/2822
• @​steaks made their first contribution in https://github.com/pmndrs/zustand/pull/2824

Full Changelog: pmndrs/zustand@v5.0.0...v5.0.1

v5.0.0

Compare Source

🎉🎉🎉 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 https://github.com/pmndrs/zustand/pull/2138
• Fix Immer type inference for setState by @​chrisvander in https://github.com/pmndrs/zustand/pull/2696

New Contributors

• @​abernier made their first contribution in https://github.com/pmndrs/zustand/pull/2674
• @​tthallos made their first contribution in https://github.com/pmndrs/zustand/pull/2501
• @​sagiereder made their first contribution in https://github.com/pmndrs/zustand/pull/2673
• @​melutovich made their first contribution in https://github.com/pmndrs/zustand/pull/2692
• @​rgksugan made their first contribution in https://github.com/pmndrs/zustand/pull/2695
• @​Anuovec made their first contribution in https://github.com/pmndrs/zustand/pull/2708
• @​EthanRBrown made their first contribution in https://github.com/pmndrs/zustand/pull/2717
• @​mym0404 made their first contribution in https://github.com/pmndrs/zustand/pull/2730
• @​87xie made their first contribution in https://github.com/pmndrs/zustand/pull/2745
• @​f312213213 made their first contribution in https://github.com/pmndrs/zustand/pull/2761
• @​DanThemes made their first contribution in https://github.com/pmndrs/zustand/pull/2764
• @​chaficnajjar made their first contribution in https://github.com/pmndrs/zustand/pull/2770
• @​goosewobbler made their first contribution in https://github.com/pmndrs/zustand/pull/2781
• @​Amyssyko made their first contribution in https://github.com/pmndrs/zustand/pull/2784
• @​MartinGamesCZ made their first contribution in https://github.com/pmndrs/zustand/pull/2785

Full Changelog: pmndrs/zustand@v4.5.5...v5.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

📦 Next.js Bundle Analysis for junat.live

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.96%. Comparing base (fd353b4) to head (8a75c0c).
Report is 93 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #506   +/-   ##
=======================================
  Coverage   87.96%   87.96%           
=======================================
  Files         128      128           
  Lines        4472     4472           
  Branches      510      510           
=======================================
  Hits         3934     3934           
  Misses        528      528           
  Partials       10       10           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.