[Snyk] Upgrade vitest from 0.31.4 to 2.0.1 #630
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.
Snyk has created this PR to upgrade vitest from 0.31.4 to 2.0.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 54 versions ahead of your current version.
The recommended version was released on 21 days ago.
Release notes
Package name: vitest
🐞 Bug Fixes
View changes on GitHub
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 #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 #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 #5047 (7f8f9)threadspool: https://vitest.dev/guide/improving-performance.html#pool--merge-reportsto support coverage - by @ AriPerkkio in #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 #5802 (dd754)indexScriptstoorchestratorScriptsin the browser config - by @ sheremet-va in #5842 (49f34)poolAPI - now requirescollectTestsmethod alongsiderunTests.excludein coverage - by @ AriPerkkio in #5997 (169bc)excludepatterns ifcoverage.excludewas overridden in the config. Add your test patterns manually, or merge your overrides with default ones:['**/my-pattern.js', ...coverageConfigDefaults.exclude]. See https://vitest.dev/config/#coverage-exclude for an example.🚀 Features
clickevent - by @ sheremet-va in #5777 (839c3)page.screenshotmethod - by @ sheremet-va in #5853 (81c42)userEventmethods, addfillanddragAndDropevents - by @ sheremet-va in #5882 (4dbea)expect.dommethod and bundlejest-dommatchers with@ vitest/browser- by @ sheremet-va in #5910 (3a96a)tripleClickto interactive api - by @ userquin in #5987 (200a4)--reporter=blobflag to generate reports and combine them withvitest --merge-reportslater!--output-json- by @ Joristdh in #5745 (0766b)parseAst,parseAstAsyncfrom vite - by @ sheremet-va (f645e)test.for- by @ hi-ogawa and @ sheremet-va in #5861 (c2380)🐞 Bug Fixes
--excludeoption - by @ fregante in #5782 (d6700)project.providetype - by @ sheremet-va in #5959 (0eda9)