Update vitest 2.1.1 → 2.1.2 (patch) #130
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vitest (2.1.1 → 2.1.2) · Repo
Release Notes
2.1.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 46 commits:
chore: release v2.1.2
fix(browser): throw an error if "@vitest/browser/context" is imported outside of the browser mode (#6570)
fix(vitest): don't start a websocket server if api is disabled (#6617)
docs: document how to mock class and its methods (#6615)
fix(vitest): make env.SSR consistent between different pools (#6616)
fix(vitest): install dependencies with the same version when prompted (#6611)
chore: specify "release" job name in CR (#6612)
docs: clarify expect.toMatchFileSnapshot (#6610)
fix(workspace): ignore DS_Store by default (#6571)
chore(deps): update dependency @rollup/plugin-commonjs to v28 (#6595)
fix(coverage): `cleanOnRerun: false` to invalidate previous results (#6592)
fix(runner): run `onTestFinished` and `onTestFailed` during `retry` and `repeats` (#6609)
refactor: replace `strip-ansi` with `stripVTControlCharacters` from `node:util` (#6608)
chore: add `pkg.pr.new` (#6362)
docs: mention `state.getFiles` API (#6607)
docs: link to default config for test timeout (#6603)
docs: clarify vi.setSystemTime (#6605)
fix(runner): guard test hook callback (#6604)
docs: link the regular guide from the advanced page (#6602)
fix(runner): fix fixture parsing of lowered async syntax for non arrow functions (#6575)
fix: move `Vitest.setServer` to post `configureServer` hook to enable import analysis for workspace config loading (#6584)
docs: deprecate `benchmark.outputFile` option (#6591)
docs: apply breaking changes of `actions/upload-artifact@v4` to example (#6597)
docs: add Profiling Test Performance guide (#6555)
docs: Mocking: Config option is called unstubEnvs, method is called unstubAllEnvs (#6579)
test: disable vmThreads test for now (#6567)
docs(config): fix spelling mistake (#6578)
fix(ui): list tests on ui when `--standalone` (#6577)
docs: add the pronounciation of vitest :) (#6497)
fix(browser): fix base for client script (#6510)
fix(browser): use `data:` protocol on preview provider file upload (#6501)
fix(browser): update solidjs testing library lib (#6548)
fix(browser): serve ui assets as static (#6564)
fix(benchmark): clear `BenchmarkResult.samples` array to reduce memory usage (#6541)
fix(browser): fix browser mock factory event race condition (#6530)
fix(runner): support fixture parsing of lowered async syntax (#6531)
fix(runner): mark tests as skipped when `beforeAll` failed (#6524)
fix(workspace): fix glob pattern detection (#6502)
fix(expect): fix `toBeDefined` with `expect.poll` (#6562)
fix(browser): fix dynamic import inside worker (#6569)
fix(coverage): include `*.astro` by default (#6565)
fix(coverage): remove empty coverage folder on test failure too (#6547)
docs: clarify
chore: fix browser package dev watch (#6523)
fix(vite-node): fix esm false-detection inside comment (#6506)
docs: fix links in mocker README (#6515)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands