chore: upgrade from vitest 2.1.8 to vitest 3.0.2 #5144
+410
−228
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
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.
Details
Vitest 3.0 Blog Post
Changelogs: v3.0.0, v3.0.1, v3.0.2
There are a lot of nice things we can make use of to improve our test utils, remove workarounds, speed up CI, etc. As a bonus, vitest-dev/vitest#6975 and other @vitest/browser improvements addresses many issues that prevented #4594 .
I also updated rollup since there's a bug fix that in theory shouldn't but might affect vitest (through vite). I'll probably undo this to keep it bisect-friendly.
A small number of snapshots had a trailing newline while all other snapshots in the same suites didn't. Vitest 2 didn't consider those a mismatch. Vitest 3 does, which is a bug fix: vitest-dev/vitest#6107 (vitest-dev/vitest#7156) .
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item