-
Notifications
You must be signed in to change notification settings - Fork 2.1k
fix(examples): correct 'test:projects' script to use vitest directly #10683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@namidapoo is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
anthonyshew
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thanks for this. Can you remove the unrelated docs changes (the newline changes and dangling commas)?
The 'test:projects' script was incorrectly using "turbo run test" instead of "vitest run", which didn't match the intended behavior of using Vitest's projects feature directly.
b265d34 to
7e043c9
Compare
@anthonyshew Thanks for the feedback! |
anthonyshew
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, let's merge!
Description
Update the
test:projectsscript in thewith-vitestexample to use Vitest's projects feature directly.Currently, the
test:projectsscript runsturbo run test, which leverages Turborepo's package-level caching. However, given the script name and the example's hybrid approach documentation, it seems more appropriate for this command to usevitest rundirectly to demonstrate Vitest's projects feature.Changes made:
package.jsonto usevitest runfor thetest:projectsscripttest:projectsdoesdocs/site/content/docs/guides/tools/vitest.mdxto reflect the correct usageTesting Instructions
examples/with-vitestdirectorypnpm installpnpm --filter @repo/vitest-config buildpnpm test- Should run tests using Turborepo (with caching)pnpm test:projects- Should run tests using Vitest's projects feature directlypnpm test:projects:watch- Should run tests in watch mode using Vitest's projects featuretestandtest:projectsnow have different behaviors as intended