Does not report TypeScript compilation errors

[lawrence-forooghian]

Describe the bug

A .ts test file which contains a TypeScript type error does not report any errors.

Reproduction

See this StackBlitz. Note line 5 of basic.test.ts, which contains a type error:

const foo: string = 10;

The tests run fine. I would have expected vitest to report some sort of compilation error.

System Info

As in StackBlitz.

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

Can you provide fully runnable reproduction? There is even no typecheck command in the provided stackblitz project.

[dim0627]

Same here

@sheremet-va
Is this what you want one?
https://stackblitz.com/edit/vitest-dev-vitest-s3v46d?file=package.json

[lawrence-forooghian]

Can you provide fully runnable reproduction? There is even no typecheck command in the provided stackblitz project.

I am referring to the npm run test:ui command that the Stackblitz project runs when you open the web page, which reports all of the tests as passing. I am surprised that a test file that contains TypeScript errors is considered to have all of its tests passing; I would have thought that vitest would

1. report a TypeScript compilation error
2. not run the tests in that file
3. report that file as in some sense "failed"

[sheremet-va]

Running type tests is a separate command. Please, refer to documentation https://vitest.dev/guide/testing-types.html

When transforming files, Vitest uses Vite which doesn't perform any type checking.

[lawrence-forooghian]

I see. Thanks for the explanation. I’ll close this issue.