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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update dependency zustand to v4 - autoclosed #39

Closed
wants to merge 1 commit into from
Closed

fix(deps): update dependency zustand to v4 - autoclosed #39

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zustand ^3.5.7 -> ^4.0.0 age adoption passing confidence

Release Notes

pmndrs/zustand (zustand)

v4.5.5

Compare Source

This improves the persist middleware behavior for an edge case.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.5.4...v4.5.5

v4.5.4

Compare Source

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

What's Changed

Full Changelog: pmndrs/zustand@v4.5.3...v4.5.4

v4.5.3

Compare Source

v4.5.2

Compare Source

It should improve the compatibility with old browsers.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.5.1...v4.5.2

v4.5.1

Compare Source

People might have misunderstood with useStore deprecation message. Hope this mitigates it.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.5.0...v4.5.1

v4.5.0

Compare Source

This version adds a new capability for SSR/Hydration.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.4.7...v4.5.0

v4.4.7

Compare Source

There's a small fix for a use case with an non-object value in store.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.4.6...v4.4.7

v4.4.6

Compare Source

v4.4.5 has an issue with some TypeScript configs about module resolution. It should be fixed now. Thanks for the patience.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.4.5...v4.4.6

v4.4.5

Compare Source

Hopefully, it should fix some issues with Node.js environment including Next.js.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.4.4...v4.4.5

v4.4.4

Compare Source

There was a tiny issue in v4.4.3, which broke with some bundlers, which this version fixes.

What's Changed

Full Changelog: pmndrs/zustand@v4.4.3...v4.4.4

v4.4.3

Compare Source

The changes in v4.4.2 were troublesome for some users. This version should fix/mitigate such cases.

What's Changed

Full Changelog: pmndrs/zustand@v4.4.2...v4.4.3

v4.4.2

Compare Source

This adds useShallow hook to cover some use cases that are deprecated with v4.4.0 change. Check out the guide.

Migration Guide

#​1991 requires something like below if you are using the devtools middleware and TypeScript.

  import { devtools } from 'zustand/middleware'
+ import type {} from '@​redux-devtools/extension'
What's Changed
New Contributors

Full Changelog: pmndrs/zustand@v4.4.1...v4.4.2

v4.4.1

Compare Source

Fixes some issues reported with the deprecated feature in v4.4.0.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.4.0...v4.4.1

v4.4.0

Compare Source

This adds new zustand/traditional entry point and deprecates equalityFn from zustand.

Migration Guide

If you don't use custom equalityFn, nothing is required.

For those who use custom equalityFn such as shallow:

// previously
import { create } from 'zustand'
const useFooStore = create((set) => ...)

// now
import { createWithEqualityFn } from 'zustand/traditional'
const useFooStore = createWithEqualityFn((set) => ..., Object.is)
// Object.is the default equalityFn which can be changed to shallow or anything else

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.9...v4.4.0

v4.3.9

Compare Source

This includes a small improvement for production build mostly for Vite users. Docs have been improved too!

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.8...v4.3.9

v4.3.8

Compare Source

For persist middleware, a new option for createJSONStorage in introduced to support more cases. Note that createJSONStorage isn't a required function (and it's not very recommended as it's not type safe), and one should create a custom storage for more use cases.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.7...v4.3.8

v4.3.7

Compare Source

This includes a couple of improvements in persist middleware.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.6...v4.3.7

v4.3.6

Compare Source

This has a little improvement for library authors.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.5...v4.3.6

v4.3.5

Compare Source

v4.3.4 has a regression in CJS build. Please use this version instead.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.4...v4.3.5

v4.3.4

Compare Source

This version fixes some build configs for some edge cases.

⚠️ this version has an issue in CJS build. Please use v4.3.5.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.3...v4.3.4

v4.3.3

Compare Source

This version includes some small fixes and internal improvements.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.2...v4.3.3

v4.3.2

Compare Source

There was a regression with default export (which is deprecated) in v4.3.0 and v4.3.1. This should fix it.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.3.1...v4.3.2

v4.3.1

Compare Source

This version supersedes v4.3.0.

What's Changed

Full Changelog: pmndrs/zustand@v4.3.0...v4.3.1

v4.3.0

Compare Source

Throughout past years of development, we've learned the (mis)usage of the library. One of our goal is to provide smallest possible APIs. To go further, this version deprecates some features. They are still usable (with warnings), but will be removed in the future.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.2.0...v4.3.0

v4.2.0

Compare Source

This version adds some new features in middleware.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.1.5...v4.2.0

v4.1.5

Compare Source

This version has several small improvements.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.1.4...v4.1.5

v4.1.4

Compare Source

This should improve some importing problems. Uncertain if it fixes everything.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.1.3...v4.1.4

v4.1.3

Compare Source

This improves store types for TS users. We also upgrade rollup. Please report issues if anyone finds any.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.1.2...v4.1.3

v4.1.2

Compare Source

This includes some fixes for edge cases. Most notably, supporting old TypeScript versions.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.1.1...v4.1.2

v4.1.1

Compare Source

In v4.1.0, there are some TypeScript type issues in redux and devtools middleware, which should be fixed.

What's Changed

Full Changelog: pmndrs/zustand@v4.1.0...v4.1.1

v4.1.0

Compare Source

This supports non-object state. It's probably one of the biggest changes in API design throughout the zustand development history. But, probably 99.9% of users won't use it 😝 .

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v4.0.0...v4.1.0

v4.0.0

Compare Source

🎉 🎉 🎉 Zustand v4 is here 🎉 🎉 🎉

Backward compatible with v3 in JS

v4 API is completely backward compatible, so it's just nothing to update if you are JS users.

One note is v4 depends on use-sync-external-store.
There might be some bundling issues.
Please report them if you encounter such cases.

TypeScript types are rewritten

To better support types with middleware, v4 TypeScript code is rewritten.
Please find docs/typescript.md for more information.

New API for context usage

In v3, zustand/context is provided as a workaround.
v4 API exposes createStore and useStore, which are more flexible.
Please read this for usage.
If you are unsure about the usage, open a new discussion.

Counter example: https://codesandbox.io/s/polished-pond-4jn1e2

Deprecated APIs are removed

Some APIs are already deprecated in v3, and they are removed in v4. Please make sure to update to the latest version of v3 before migrating to v4.

What's Changed

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 becomes conflicted, 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
Copy link
Author

renovate bot commented Sep 25, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @testing-library/cypress@6.0.1
npm ERR! Found: cypress@6.9.1
npm ERR! node_modules/cypress
npm ERR!   dev cypress@"^6.6.0" from the root project
npm ERR!   cypress@"*" from @types/testing-library__cypress@5.0.9
npm ERR!   node_modules/@types/testing-library__cypress
npm ERR!     @types/testing-library__cypress@"^5.0.6" from @testing-library/cypress@6.0.1
npm ERR!     node_modules/@testing-library/cypress
npm ERR!       dev @testing-library/cypress@"^6.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cypress@"^2.1.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @testing-library/cypress@6.0.1
npm ERR! node_modules/@testing-library/cypress
npm ERR!   dev @testing-library/cypress@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: cypress@5.6.0
npm ERR! node_modules/cypress
npm ERR!   peer cypress@"^2.1.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @testing-library/cypress@6.0.1
npm ERR!   node_modules/@testing-library/cypress
npm ERR!     dev @testing-library/cypress@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-09-26T07_43_53_415Z-debug-0.log

@renovate renovate bot force-pushed the renovate/zustand-4.x branch 3 times, most recently from bf13f05 to 02ce4e0 Compare September 25, 2024 17:12
@renovate renovate bot force-pushed the renovate/zustand-4.x branch from 02ce4e0 to 2face0f Compare September 26, 2024 07:44
@renovate renovate bot changed the title fix(deps): update dependency zustand to v4 fix(deps): update dependency zustand to v4 - autoclosed Oct 17, 2024
@renovate renovate bot closed this Oct 17, 2024
@renovate renovate bot deleted the renovate/zustand-4.x branch October 17, 2024 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants