You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer using Vitest I want common build outputs created excluded so that duplicate versions of tests don't run, and it's easier to get set up without having to provide more config.
Currently the defaultExclude has rules for karma, rollup, webpack, vite, vitest, jest, ava, babel, nyc, cypress, tsup, eslint and prettier.
I would argue that both next and turbo are projects with higher usage levels than some in this list, and therefore it's reasonable to include them.
Clear and concise description of the problem
As a developer using Vitest I want common build outputs created excluded so that duplicate versions of tests don't run, and it's easier to get set up without having to provide more config.
Currently the defaultExclude has rules for karma, rollup, webpack, vite, vitest, jest, ava, babel, nyc, cypress, tsup, eslint and prettier.
I would argue that both next and turbo are projects with higher usage levels than some in this list, and therefore it's reasonable to include them.
Suggested solution
Alternative
Tell users to manually exclude these files.
Additional context
I'm happy to submit a PR for this.
Validations
The text was updated successfully, but these errors were encountered: