-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Add vitest ^2 to peerDependencies of @fast-check/vitest #5114
Comments
Funny, came here to say the same thing! |
I was working on it recently on #5108. It should be there soon |
It seems that Vitest v2 broke part of fast-check. The broken part is around stack overflows at shrink time. While there is probably nothing to worry about, I may issue separately the bump and the peer-dep change. So far to unlock users, I'll just bump the peer stuff. |
Interesting. That sounds like a good plan. FWIW I'm using vitest 2 with fast-check right now and haven't noticed any problems so far. |
Published at 0.1.2. I succeed into bumping without fixing anything in fast-check, it was mostly a side-effect of a change on their side but the impact is null for fast-check's users. |
🚀 Feature Request
Support vitest 2.x in peerDependencies.
Motivation
I get a peer dependency warning when using vitest 2.0.1.
Vitest 2 and @fast-check/vitest are working fine in my current project, FWIW.
The text was updated successfully, but these errors were encountered: