docs: update wording to Vitest 3.0 #7351
Open
+1
−1
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
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
sheremet-va
requested changes
Jan 23, 2025
| @@ -21,7 +21,7 @@ test('validation works', { retry: 3 }, () => { // [!code ++] | |||
| }) | |||
| ``` | |||
|
|
|||
| Vitest 4.0 will throw an error if the third argument is an object. Note that the timeout number is not deprecated: | |||
| Vitest 3.0 will throw an error if the third argument is an object. Note that the timeout number is not deprecated: | |||
There was a problem hiding this comment.
Vitest 3 is out and it doesn't throw an error, it prints a warning (see paragraph above)
Vitest 4 (the next major) however will throw an error
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.
Description
I noticed that some parts of the migration guide referred to Vitest 4.0, which I believe should be Vitest 3.0. Then, I’ve updated it.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.If you have any feedback or suggestions, please let me know.