Bump zustand from 4.5.5 to 5.0.1 in /frontend

[dependabot[bot]]

Bumps zustand from 4.5.5 to 5.0.1.

Release notes

Sourced from zustand's releases.

v5.0.1

This fixes shallow function for some edge cases.

What's Changed

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

New Contributors

• @​legcy143 made their first contribution in pmndrs/zustand#2799
• @​kretajak made their first contribution in pmndrs/zustand#2822
• @​steaks made their first contribution in pmndrs/zustand#2824

Full Changelog: https://github.com/pmndrs/zustand/compare/v5.0.0...v5.0.1

v5.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.

... (truncated)

Commits

• c87a5d6 5.0.1
• 1068ff9 chore(deps): update dev dependencies (#2826)
• 9525f92 fix(shallow): iterable-like insensitive keys order comparison (alternate impl...
• dfbed9c docs: add leo-query to third-party libraries list (#2824)
• 064be30 test: calculate coverage for src files only (#2822)
• 259c19f fix(shallow): fallback map-like iterator comparison (#2795)
• f9b5538 Update use-store.md (#2799)
• cce8d5b chore: fix middleware imports (#2798)
• 0007ef4 remove tag:next packageConfig
• 5408e01 5.0.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)