Update vitest monorepo to v2 (major) #573
Merged
+145
−176
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.
This PR contains the following updates:
1.6.0
->2.0.1
1.6.0
->2.0.1
Release Notes
vitest-dev/vitest (vite-node)
v2.0.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.0.0
Compare Source
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
🚨 Breaking Changes
--segfault-retry
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5514 (ed60e)threads
segfaults. Our current recommendation is to use the new defaultforks
pool instead.onTestFinished
hook. This can make your tests run a little bit slower.coverage.ignoreEmptyLines
by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5543 (31994)location
field pointed to the error location instead of the test location. Now it is aligned with jest and contains theline
andcolumn
of a test function, but requiresincludeTaskLocation
to be enabled.pool
to'forks'
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5047 (7f8f9)threads
pool: https://vitest.dev/guide/improving-performance.html#pool--merge-reports
to support coverage - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5736 (b7438)spy.mock.returns
. If the function is async or returns a promise, it will always succeed and have aPromise
inresults
. To make migration easier, we introducedspy.mock.settledResults
that unwraps promises andexpect().toHaveResolved()
matcher that accepts unwrapped value.json
output - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5802 (dd754)indexScripts
toorchestratorScripts
in the browser config - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5842 (49f34)pool
API - now requirescollectTests
method alongsiderunTests
.exclude
in coverage - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5997 (169bc)exclude
patterns ifcoverage.exclude
was overridden in the config. Add your test patterns manually, or merge your overrides with default ones:['**/my-pattern.js', ...coverageConfigDefaults.exclude]
.🚀 Features
click
event - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5777 (839c3)page.screenshot
method - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5853 (81c42)userEvent
methods, addfill
anddragAndDrop
events - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5882 (4dbea)expect.dom
method and bundlejest-dom
matchers with@vitest/browser
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5910 (3a96a)tripleClick
to interactive api - by @userquin in https://github.com/vitest-dev/vitest/issues/5987 (200a4)--output-json
- by @Joristdh in https://github.com/vitest-dev/vitest/issues/5745 (0766b)parseAst
,parseAstAsync
from vite - by @sheremet-va (f645e)test.for
- by @hi-ogawa and @sheremet-va in https://github.com/vitest-dev/vitest/issues/5861 (c2380)🐞 Bug Fixes
--exclude
option - by @fregante in https://github.com/vitest-dev/vitest/issues/5782 (d6700)project.provide
type - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5959 (0eda9)preview
provider when running in StackBlitz - by @userquin in https://github.com/vitest-dev/vitest/issues/5836 (76e13)coverage.reporter
from string values - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5920 (f33da)thresholds.autoUpdate
to supportmergeConfig
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5818 (7afb3)stderr
ofstartVitest()
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5954 (70805)else
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6014 (368c1)test-exclude
to v7 - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5867 (0a715)poolOptions.<name>.isolate
fromforks
options - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5840 (a60a1)toMatchFileSnapshot
with empty file - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5894 (88006)FileDetails
title status icon not being updated - by @userquin in https://github.com/vitest-dev/vitest/issues/5942 (e9ddf)VITE_
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6017 (d87be)provide
to the public API - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5897 (66e64)View changes on GitHub
Configuration
📅 Schedule: Branch creation - "on the first saturday of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.