feat: deprecate workspace in favor of projects
#7923
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
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
AriPerkkio
reviewed
May 3, 2025
AriPerkkio
reviewed
May 4, 2025
Co-authored-by: Ari Perkkiö <[email protected]>
AriPerkkio
previously approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
In an effort to simplify the configuration, the team decided to deprecate the separate
vitest.workspacefile and recommend using only theprojectsoption in the root config. This also simplifies how the global options are configured (because you don't need to guess how to add reporters when you have no root config)We also decided to deprecate the
workspacename because it clashes with other tools like PNPM that provide the monorepo support via this option. Vitest doesn't run these projects with separateCWDand treates them more like sub-Vitests. It also gives us more space to come up with a better solution for monorepos without breaking others.