@vitest/expect
5.0.5 · 15 Oct 2026MIT151.9M / weekRepositoryHomepagenpmAtom feed
Upgrading @vitest/expect from 3.1.2 to 3.2.7
10 releases in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 23
- new
- 67
- fixes
Before you upgrade
Tick each one off as you go- deprecated3.2.0
Release by release
- fixed
browser: Check fs access in builtin commands [backport to v3]
- fixed
- fixed
Pin last supported vite-node version
- fixed
- new
api: Add
allowWriteandallowExecoptions toapi[backport to v3] - fixed
browser: Disable client
cdpAPI whenallowWrite/allowExec: false[backport to v3]
- new
- fixed
Use correct path for optimisation of strip-literal
- fixed
Print uint and buffer as a simple string
- fixed
browser: Show a helpful error when spying on an export
- fixed
cli:
vitest run --watchshould be watch-mode
- fixed
- new
browser: Use base url instead of vitest
- new
ui: Show test annotations and metadata in the test report tab
- fixed
Rerun tests when project's setup file is changed
- fixed
Revert
expect.anyreturn type
- new
- new
Support rolldown-vite
- fixed
browser: Calculate prepare time from
createTesterscall on the main thread - fixed
browser: Optimize build output and always prebundle vitest
- fixed
browser: Make custom locators available in
vitest-browser-*packages - fixed
expect: Ensure we can always self
toEqual - fixed
reporter: Allow
dotreporter to work in non interactive terminals
- new
- fixed
Use sha1 instead of md5 for hashing
- fixed
expect: Fix chai import in dts
- fixed
expect: Export
DeeplyAllowMatchers
- fixed
- new
Provide
ctx.signal - new
Support custom colors for
test.name - new
Add
vi.mockObjectto automock any object - new
Introduce
watchTriggerPatternsoption
- new