chore(deps): update dependency vitest to v2 #726
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.
This PR contains the following updates:
^1.0.0->^2.0.0Release Notes
vitest-dev/vitest (vitest)
v2.0.0Compare 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)threadssegfaults. Our current recommendation is to use the new defaultforkspool instead.onTestFinishedhook. This can make your tests run a little bit slower.coverage.ignoreEmptyLinesby default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5543 (31994)locationfield pointed to the error location instead of the test location. Now it is aligned with jest and contains thelineandcolumnof a test function, but requiresincludeTaskLocationto be enabled.poolto'forks'- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5047 (7f8f9)threadspool: https://vitest.dev/guide/improving-performance.html#pool--merge-reportsto 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 aPromiseinresults. To make migration easier, we introducedspy.mock.settledResultsthat unwraps promises andexpect().toHaveResolved()matcher that accepts unwrapped value.jsonoutput - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5802 (dd754)indexScriptstoorchestratorScriptsin the browser config - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5842 (49f34)poolAPI - now requirescollectTestsmethod alongsiderunTests.🚀 Features
--output-json- by @Joristdh in https://github.com/vitest-dev/vitest/issues/5745 (0766b)parseAst,parseAstAsyncfrom vite - by @sheremet-va (f645e)clickevent - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5777 (839c3)page.screenshotmethod - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5853 (81c42)userEventmethods, addfillanddragAndDropevents - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5882 (4dbea)expect.dommethod and bundlejest-dommatchers with@vitest/browser- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5910 (3a96a)tripleClickto interactive api - by @userquin in https://github.com/vitest-dev/vitest/issues/5987 (200a4)test.for- by @hi-ogawa and @sheremet-va in https://github.com/vitest-dev/vitest/issues/5861 (c2380)🐞 Bug Fixes
--excludeoption - by @fregante in https://github.com/vitest-dev/vitest/issues/5782 (d6700)project.providetype - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5959 (0eda9)previewprovider when running in StackBlitz - by @userquin in https://github.com/vitest-dev/vitest/issues/5836 (76e13)coverage.reporterfrom string values - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5920 (f33da)thresholds.autoUpdateto supportmergeConfig- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5818 (7afb3)stderrofstartVitest()- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5954 (70805)exclude- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5997 (169bc)else- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6014 (368c1)test-excludeto v7 - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5867 (0a715)poolOptions.<name>.isolatefromforksoptions - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5840 (a60a1)toMatchFileSnapshotwith empty file - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5894 (88006)FileDetailstitle 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)provideto the public API - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5897 (66e64)View changes on GitHub
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.