[Snyk] Upgrade vitest from 1.6.0 to 2.1.2 #12
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 1.6.0 to 2.1.2.
ℹ️ 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 28 versions ahead of your current version.
The recommended version was released on 25 days ago.
Release notes
Package name: vitest
🐞 Bug Fixes
Vitest.setServer
to postconfigureServer
hook to enable import analysis for workspace config loading - by @ hi-ogawa in #6584 (e7f35)BenchmarkResult.samples
array to reduce memory usage - by @ hi-ogawa and @ AriPerkkio in #6541 (a6407)data:
protocol on preview provider file upload - by @ userquin in #6501 (e9821)*.astro
by default - by @ AriPerkkio in #6565 (f8ff7)cleanOnRerun: false
to invalidate previous results - by @ AriPerkkio in #6592 (88bde)toBeDefined
withexpect.poll
- by @ hi-ogawa in #6562 (f7da6)--cpu-prof
and--heap-prof
not working by default - by @ AriPerkkio in #6555 (2e4d894)beforeAll
failed - by @ hi-ogawa in #6524 (fb797)onTestFinished
andonTestFailed
duringretry
andrepeats
- by @ hi-ogawa in #6609 (c5e29)--standalone
- by @ hi-ogawa in #6577 (d0bf8)View changes on GitHub
🐞 Bug Fixes
View changes on GitHub
This release makes another big change to the Browser Mode by introducing locators API:
const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the
page
object from@ vitest/browser/context
.Potential Breaking Change
vitest.config.ts
orvite.config.ts
inside the folder)projects/*
will match anything inside theprojects
folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config.projects/**/*
previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects
.🚀 Features
userEvent.upload
in playwright provider - by @ sheremet-va in #6442 (cf148)--inspect
- by @ AriPerkkio in #6433 (0499a)--inspect-brk
- by @ AriPerkkio in #6434 (7ab0f)--exclude-after-remap
- by @ AriPerkkio in #6309 (5932a){ spy: true }
instead of a factory - by @ sheremet-va in #6289 (95f02)vi.advanceTimersToNextFrame
- by @ bnjm and @ sheremet-va in #6347 (8ff63)fast-glob
totinyglobby
- by @ SuperchupuDev in #6274 (c321a)🐞 Bug Fixes
index
file - by @ sheremet-va in #6266 (081cf)expect.getState().testPath
always returns correct path - by @ sheremet-va in #6472 (ac698)vitest
and@ vitest/*
versions don't match - by @ AriPerkkio in #6317 (e662c)vitenode
for uncovered files - by @ AriPerkkio in #6044 (da52d)performance.now
instead ofDate.now
for duration - by @ LuciNyan in #6382 (fe489)toMatchInlineSnapshot
updates at the same location - by @ hi-ogawa in #6332 (1606f)typecheck.include
overlaps withinclude
- by @ sheremet-va in #6256 (153ff)