docs: upgrades for Vitest doc and add with-vitest example
#10063
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
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
anthonyshew
commented
Mar 4, 2025
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
Some iterations for our Vitest documentation:
with-vitestexampleCloses #4517
Reviewer note
The example does exactly one thing that I don't love, in that it doesn't have dependencies between
turbo run testand the set of tasks that do the merging/reporting of coverage after that. This means you have to doturbo run test && whatever-elserather than a singularturbocommand.I don't know if there's a great way to model this in our DSL right now, so I left it out. Ultimately, running
turbo run test && ...isn't too big of a deal, right?...Right?Testing Instructions
👀