Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 15, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zustand 4.5.6 -> 5.0.3 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

pmndrs/zustand (zustand)

v5.0.3

Compare Source

ExtractState is a type util to extract state type from store type.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v5.0.2...v5.0.3

v5.0.2

Compare Source

v5.0.1

Compare Source

This fixes shallow function for some edge cases.

What's Changed

New Contributors

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

New Contributors

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


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/London, 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.

@renovate renovate bot force-pushed the renovate/zustand-5.x branch 8 times, most recently from f443221 to 58c0a71 Compare October 22, 2024 04:08
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 16 times, most recently from fc14a44 to 7ba57cf Compare October 29, 2024 07:47
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 6 times, most recently from cb6b76b to ababbb6 Compare November 1, 2024 04:38
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 14 times, most recently from 57544dc to 251cedb Compare January 26, 2025 13:28
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 4 times, most recently from 84450b0 to 7487740 Compare January 27, 2025 04:24
@renovate renovate bot force-pushed the renovate/zustand-5.x branch from 7487740 to 0de12bd Compare February 11, 2025 11:28
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 5 times, most recently from 27666be to 2226b4a Compare February 25, 2025 10:34
@renovate renovate bot force-pushed the renovate/zustand-5.x branch 2 times, most recently from 5c04d0a to 6de4b47 Compare April 8, 2025 17:00
@renovate renovate bot force-pushed the renovate/zustand-5.x branch from 6de4b47 to 8795048 Compare April 30, 2025 12:29
@mjfwebb mjfwebb merged commit 1bb1ad3 into dev Apr 30, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants