✨(vitest) Get rid of deprecated vitest/suite imports#6766
Conversation
🦋 Changeset detectedLatest commit: 90ed207 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@fast-check/ava
fast-check
@fast-check/jest
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
6fb1d88 to
8c94ff3
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6766 +/- ##
=======================================
Coverage 94.52% 94.52%
=======================================
Files 210 210
Lines 5685 5685
Branches 1498 1498
=======================================
Hits 5374 5374
Misses 298 298
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
nielk
changed the title
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@fast-check/vitest': patch | |||
There was a problem hiding this comment.
Probably a major? I feel that the peerDep range for vitest might not be valid anymore. Put minor if confirmed (we want to stay at 0.x atm)
|
@nielk Thanks a lot for the contribution. I just updated your PR with a few changes to change our peer requirements. I may wait a few weeks before releasing the version to wait for our users to be on vitest 4.1 but I'll release it soon anyway |
dubzzz
changed the title
|
@claude propose a new PR to adapt the readme of fast-check/vitest to explain our requirements for 0.4.0 based on newly introduced changes |
|
Claude finished @dubzzz's task in 1m 14s —— View job • Updating README for @fast-check/vitest 0.4.0 requirements
Added a new row for 0.4 in the minimal requirements table documenting the · |
## Description Update the minimal requirements table in the `@fast-check/vitest` README to document the new vitest ^4.1.0 peer dependency requirement for version 0.4.0. Related to #6766 ## Checklist — _Don't delete this checklist and make sure you do the following before opening the PR_ - [x] I have a full understanding of every line in this PR — whether the code was hand-written, AI-generated, copied from external sources or produced by any other tool - [ ] I flagged the impact of my change (minor / patch / major) either by running `pnpm run bump` or by following the instructions from the changeset bot - [x] I kept this PR focused on a single concern and did not bundle unrelated changes - [x] I followed the [gitmoji](https://gitmoji.dev/) specification for the name of the PR, including the package scope (e.g. `🐛(vitest) Something...`) when the change targets a package other than `fast-check` - [ ] I added relevant tests and they would have failed without my PR (when applicable) Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Nicolas DUBIEN <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2 participants
Description
Importing from
vitest/suiteis now deprecated since Vitest 4.1.When executing
vitesttests withfast-check/vitestwe get theses warnings:This pull-request use static methods of "TestRunner" from the "vitest" entry point instead of "vitest/suite". (deprecated since Vitest 4.1)
Fixes #6746
Checklist
— Don't delete this checklist and make sure you do the following before opening the PR
pnpm run bumpor by following the instructions from the changeset bot🐛(vitest) Something...) when the change targets a package other thanfast-check