Skip to content

Add .next and .turbo to defaultExclude #5579

@domdomegg

Description

@domdomegg

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    p2-to-be-discussedEnhancement under consideration (priority)

    Type

    No type

    Projects

    Status

    Rejected

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions