Skip to content
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

Recommend using vitest.workspace if too many vitest.config files are found #299

Closed
4 tasks done
sheremet-va opened this issue Mar 16, 2024 · 0 comments
Closed
4 tasks done
Labels
p2-nice-to-have Not breaking anything but nice to have (priority)

Comments

@sheremet-va
Copy link
Member

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

@sheremet-va sheremet-va added the p2-nice-to-have Not breaking anything but nice to have (priority) label Mar 16, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p2-nice-to-have Not breaking anything but nice to have (priority)
Projects
None yet
Development

No branches or pull requests

1 participant