vitest-dev/vitest
v5.1.0Curated build tool / testing repository (vitest-dev/vitest) tracked via conditional GitHub .atom polling.
vitest is an open-source library and developer tool in the vitest-dev/vitest ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.
Add --last-failed to run only failed tests - by @shereme. Drop-in upgrade. Migration: None.
Key Release Highlights (v5.1.0)
- Add
--last-failedto run only failed tests - by @sheremet-va in #11558 (82f63) - Support
Temporal.InstantandTemporal.ZonedDateTimeinvi.setSystemTime()- by @Prajwal2246, Prajwal2246, Claude Opus 5.5 (1M context), @hi-ogawa and **Codex (GPT-... - Introduce
--since-last-runflag - by @sheremet-va in #11516 (08bd9) - Expose per-retry/repeat attempt result - by @hi-ogawa, Codex (GPT-6) and Claude Opus 5.5 (1M context) in #11232 (21be4)
Verified safe drop-in upgrade for vitest in package.json.
npm install vitest@5.1.0Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Add --last-failed to run only failed tests - by @shereme. Drop-in upgrade. Migration: None.
Upgrade & Migration Q&A (vitest-dev/vitest v5.1.0)
Direct Answers for Engineers & AI AgentsIs vitest-dev/vitest v5.1.0 safe to upgrade in production?
vitest-dev/vitest v5.1.0 is classified as COMPATIBLE (MINOR release). Add --last-failed to run only failed tests - by @shereme. Drop-in upgrade. Migration: None.
What breaking changes or compatibility risks exist in vitest-dev/vitest v5.1.0?
No breaking API changes or peer dependency conflicts are recorded for vitest-dev/vitest v5.1.0 in the RepoSense compatibility graph.
What is the bundle size impact of vitest v5.1.0?
Measured bundle size telemetry is currently unavailable for vitest v5.1.0; verify build output locally before deploying.
How do I upgrade vitest to v5.1.0?
Upgrade vitest to v5.1.0 by running "npm install vitest@5.1.0" and applying the migration steps: npm install vitest@5.1.0