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
Is your feature request related to a problem? Please describe.
Currently, when running Vitest with vite-plugin-checker configured, checker errors are only logged and do not fail the test run. This is particularly apparent when using the TypeScript checker, as tools like ts-jest treat type errors as test failures by default.
Describe the solution you'd like
An MVP would be:
Detection of any TypeScript errors can (configurably) result in the whole Vitest run failing
Behaviour is configurable via a boolean flag specific to the TypeScript checker
The ideal solution would be:
Any checker errors can (configurably) result in failures of the individual tests (or test files) they appear in
Behaviour is configurable via boolean flags specific to each checker implementation
Is your feature request related to a problem? Please describe.
Currently, when running Vitest with
vite-plugin-checker
configured, checker errors are only logged and do not fail the test run. This is particularly apparent when using the TypeScript checker, as tools likets-jest
treat type errors as test failures by default.Describe the solution you'd like
An MVP would be:
The ideal solution would be:
Describe alternatives you've considered
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: