Document considerations when using Vitest #81
Merged
Conversation
This file contains hidden or 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
acelaya
commented
May 22, 2025
| "vitest": { | ||
| "optional": true | ||
| } | ||
| }, |
There was a problem hiding this comment.
I have checked that all projects that depend on this library are already using vitest as well.
acelaya
force-pushed
the
vitest-docs
branch
2 times, most recently
from
26ce3c7 to
d00834e
Compare
robertknight
approved these changes
May 23, 2025
This was referenced May 23, 2025
Merged
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.
This PR extends the documentation on how we use Vitest, explaining the differences between our setup and the standard assumptions Vitest does.
One thing all projects need to do when using Vitest is defining to options when using
babel-plugin-istanbul. This library now exposes an object with those options, so that we don't need to repeat them in every project with a comment explaining why they need to be set.Additionally, this makes Vitest no longer an optional dependency, and exports everything in the
vitestmodule from the main entry point.The
/vitestentry point has been preserved for backwards compatibility, but it is now mostly redundant.