We are deprecating the `@vitest/browser/context` in the next version of Vitest in favor of `vitest/browser`. The provider is now also required for better type safety (providers are also moved to separate packages to improve the size and dependency graph of @vitest/browser)
September 30, 2025 at 2:22 PM
We are deprecating the `@vitest/browser/context` in the next version of Vitest in favor of `vitest/browser`. The provider is now also required for better type safety (providers are also moved to separate packages to improve the size and dependency graph of @vitest/browser)
Vitest 4 runs simple test files faster! You can already check it out by installing Vitest 4 beta. On average, Vitest now takes 25% less time to start the test. Due to parallelisation, the overall time difference can vary.
We are focusing our efforts on improving the time even more in the next beta!
August 27, 2025 at 3:29 PM
Vitest 4 runs simple test files faster! You can already check it out by installing Vitest 4 beta. On average, Vitest now takes 25% less time to start the test. Due to parallelisation, the overall time difference can vary.
We are focusing our efforts on improving the time even more in the next beta!
In the next version of Vitest a test will fail if you forgot to await .poll or .element assertions! .rejects and .resolves also print a warning now, but don’t fail a test yet (coming in Vitest 3)
November 8, 2024 at 3:25 PM
In the next version of Vitest a test will fail if you forgot to await .poll or .element assertions! .rejects and .resolves also print a warning now, but don’t fail a test yet (coming in Vitest 3)