[Snyk] Upgrade vitest from 0.34.6 to 2.0.3 #649
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.34.6 to 2.0.3.
ℹ️ 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 43 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: vitest
🚀 Features
🐞 Bug Fixes
--inspect-brk
stop on Windows - by @ AriPerkkio in #6110 (f8519)vi.spyOn
toMockInstance
of function overload - by @ hi-ogawa in #6086 (e9f9a)View changes on GitHub
🐞 Bug Fixes
crypto.randomUUID
from the client - by @ userquin in #6079 (04c83)vitest
- by @ AriPerkkio in #6060 (95a2d)🏎 Performance
View changes on GitHub
🐞 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)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 #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 #5047 (7f8f9)threads
pool: https://vitest.dev/guide/improving-performance.html#pool--merge-reports
to 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 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 #5802 (dd754)indexScripts
toorchestratorScripts
in the browser config - by @ sheremet-va in #5842 (49f34)pool
API - now requirescollectTests
method alongsiderunTests
.exclude
in coverage - by @ AriPerkkio in #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]
. See https://vitest.dev/config/#coverage-exclude for an example.🚀 Features
click
event - by @ sheremet-va in #5777 (839c3)page.screenshot
method - by @ sheremet-va in #5853 (81c42)userEvent
methods, addfill
anddragAndDrop
events - by @ sheremet-va in #5882 (4dbea)expect.dom
method and bundlejest-dom
matchers with@ vitest/browser
- by @ sheremet-va in #5910 (3a96a)tripleClick
to interactive api - by @ userquin in #5987 (200a4)--reporter=blob
flag to generate reports and combine them withvitest --merge-reports
later!--output-json
- by @ Joristdh in #5745 (0766b)parseAst
,parseAstAsync
from vite - by @ sheremet-va (f645e)test.for
- by @ hi-ogawa and @ sheremet-va in #5861 (c2380)🐞 Bug Fixes
--exclude
option - by @ fregante in #5782 (d6700)