Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OPHJOD-851: Upgrade zustand from 5.0.0-rc.2 to 5.0.0 #260

Closed
wants to merge 1 commit into from

Conversation

snyk-io[bot]
Copy link
Contributor

@snyk-io snyk-io bot commented Nov 10, 2024

snyk-top-banner

Snyk has created this PR to upgrade zustand from 5.0.0-rc.2 to 5.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: zustand
  • 5.0.0 - 2024-10-14

    🎉🎉🎉 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: v4.5.5...v5.0.0

  • 5.0.0-rc.2 - 2024-09-15

    Hopefully, this will be the last RC, unless we have serious bug reports in #2741.

    What's Changed

    New Contributors

    Full Changelog: v5.0.0-rc.1...v5.0.0-rc.2

from zustand GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Copy link

sonarcloud bot commented Nov 10, 2024

@ketsappi
Copy link
Contributor

Päivitetty jo toisen PR yhteydessä: #254

@ketsappi ketsappi closed this Nov 11, 2024
@ketsappi ketsappi deleted the snyk-upgrade-738cba3431612e2e593f8088329e5f5c branch November 12, 2024 10:25
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.

1 participant