Issues: vitest-dev/vitest ... Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community ...

Issues: vitest-dev/vscode ... Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community ...

23 июл. 2024 г. · This error happens when vi.mock method is called on a module that was already loaded. Vitest throws this error because this call has no effect since cached ...

29 окт. 2024 г. · To create a Vitest configuration file, follow the guide. Make sure you understand how Vitest config resolution works before proceeding.

6 окт. 2024 г. · React testing library has the same performance impact on both jest and vitest. The principle issue I found with vitest is choosing the right kind of threading.

2 янв. 2023 г. · Vitest is faster only if you turn off test isolation. Yep, that's the current recommended solution from one of the developers.

28 мая 2023 г. · The problem is that these global types exist both in Vitest and Jest, so there's a conflict. There's an issue opened on GitHub Jest-dom for this issue.

11 февр. 2023 г. · Looking around online articles and GitHub issues on Vitest, it looks like Jest is still just as fast or faster than Vitest in normal test runs (not watch mode).

11 мая 2023 г. · The following is a summary of the Vitest GitHub issue "Vitest runs tests 3x slower than Jest", which if printed would require about 24 pages ...

I can run the tests from the command line without problems. When I put the file vitest.config.ts into a subdirectory the configuration works.