-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Feature
Copy link
Labels
enhancement: pending triagep2-to-be-discussedEnhancement under consideration (priority)Enhancement under consideration (priority)
Description
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
| 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:
- Enable --typecheck by default? #7773: filed last year, still awaiting triage
- 🛠 Tooling: "Testing types with tsc and vue-tsc is an experimental feature." spam in tests flint-fyi/flint#2398: we're in a monorepo with projects such that 33 of these logs are written upon every root-level
pnpm test(😭)
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancement: pending triagep2-to-be-discussedEnhancement under consideration (priority)Enhancement under consideration (priority)
Type
Projects
Status
P2 - 2