Clear and concise description of the problem
Right now, when you run with typecheck enabled, this warning is emitted:
|
logger.console.warn( |
|
c.yellow( |
|
'Testing types with tsc and vue-tsc is an experimental feature.\nBreaking changes might not follow SemVer, please pin Vitest\'s version when using it.', |
|
), |
|
) |
Testing types with tsc and vue-tsc is an experimental feature.
Breaking changes might not follow SemVer, please pin Vitest's version when using it.
That's good to know when setting up the typecheck feature. But if a project is already using the feature, it can become kind of a lot. Especially in monorepos where multiple instances of Vitest get run.
Suggested solution
Could we have an option to say "yes, I know this is experimental, don't log"? Or at least only log once per system, determined by writing to a cache?
Alternative
...or stabilize the typecheck feature?
Additional context
Related:
Validations
Clear and concise description of the problem
Right now, when you run with typecheck enabled, this warning is emitted:
vitest/packages/vitest/src/node/config/resolveConfig.ts
Lines 791 to 795 in b0b83e2
That's good to know when setting up the typecheck feature. But if a project is already using the feature, it can become kind of a lot. Especially in monorepos where multiple instances of Vitest get run.
Suggested solution
Could we have an option to say "yes, I know this is experimental, don't log"? Or at least only log once per system, determined by writing to a cache?
Alternative
...or stabilize the typecheck feature?
Additional context
Related:
pnpm test(😭)Validations