Vitest doesn't need a configuration file to run, in case the defaults are enough for the project. For example, a Node package.
But the extension doesn't work without the configuration file, so I'd be adding an empty vitest.config.ts solely to get the extension going.
Suggested solution
Judging by the output the extension already detects the vitest package being installed, so the suggestion is for the extension to respond only to that, rather than also needing the configuration file.
Clear and concise description of the problem
Vitest doesn't need a configuration file to run, in case the defaults are enough for the project. For example, a Node package.
But the extension doesn't work without the configuration file, so I'd be adding an empty
vitest.config.ts
solely to get the extension going.Suggested solution
Judging by the output the extension already detects the
vitest
package being installed, so the suggestion is for the extension to respond only to that, rather than also needing the configuration file.Validations