chore: upgrade to vitest v2 #96
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aleclarson
force-pushed
the
main
branch
2 times, most recently
from
2154f96 to
6a4b4f6
Compare
3 tasks
aleclarson
force-pushed
the
chore/vitest-upgrade
branch
from
c9aff26 to
46a8ce4
Compare
|
A new beta version To install: pnpm add [email protected]The 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tip
The owner of this PR can publish a preview release by commenting
/publishin this PR. Afterwards, anyone can try it out by runningpnpm add radashi@pr<PR_NUMBER>.Summary
No particular reason to rush this upgrade (I was seeing a “hanging process” issue that prevented Vitest from exiting before a 10 second timeout. But opening this in case someone wants to investigate.
Vitest 1.6.0 --> 2.0.1
For any code change,
Does this PR introduce a breaking change?
No