-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed as not planned
Labels
p2-to-be-discussedEnhancement under consideration (priority)Enhancement under consideration (priority)
Description
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
+export const defaultExclude = ['**/node_modules/**', '**/dist/**', '**/cypress/**', '**/.{idea,git,cache,output,temp,next,turbo}/**', '**/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*']
-export const defaultExclude = ['**/node_modules/**', '**/dist/**', '**/cypress/**', '**/.{idea,git,cache,output,temp}/**', '**/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*']
Alternative
Tell users to manually exclude these files.
Additional context
I'm happy to submit a PR for this.
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Metadata
Metadata
Assignees
Labels
p2-to-be-discussedEnhancement under consideration (priority)Enhancement under consideration (priority)
Type
Projects
Status
Rejected