Recommend using vitest.workspace
if too many vitest.config
files are found
#299
Labels
p2-nice-to-have
Not breaking anything but nice to have (priority)
Clear and concise description of the problem
The recommended way to use Vitest in a monorepo is to use Vitest Workspace feature.
Suggested solution
If we find too many vitest config files (3 or more), we should show a notification with a button that creates a workspace file. There should also be a way to disable this notification in case this is a desirable behavior.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: