forked from RSSNext/Follow
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Snyk] Upgrade vitest from 2.0.5 to 2.1.0 #3
Open
nerdy-tech-com-gitub
wants to merge
12
commits into
dev
Choose a base branch
from
snyk-upgrade-7ad979753328e4f23db4c7b8bd379dc4
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[Snyk] Upgrade vitest from 2.0.5 to 2.1.0 #3
nerdy-tech-com-gitub
wants to merge
12
commits into
dev
from
snyk-upgrade-7ad979753328e4f23db4c7b8bd379dc4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade vitest from 2.0.5 to 2.1.0. See this package in npm: vitest See this project in Snyk: https://app.snyk.io/org/nerds-github/project/324ac84e-21d5-41e5-8851-87b6c10024d0?utm_source=github&utm_medium=referral&page=upgrade-pr
Stale pull request message |
nerdy-tech-com-gitub
force-pushed
the
dev
branch
from
December 3, 2024 18:35
b55fee7
to
5c4b5f0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 2.0.5 to 2.1.0.
ℹ️ 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 8 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: vitest
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)View changes on GitHub
🚀 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){ spy: true }
instead of a factory - by @ sheremet-va in #6289 (95f02)🐞 Bug Fixes
performance.now
instead ofDate.now
for duration - by @ LuciNyan in #6382 (fe489)View changes on GitHub
🚀 Features
--exclude-after-remap
- by @ AriPerkkio in #6309 (5932a)vi.advanceTimersToNextFrame
- by @ bnjm and @ sheremet-va in #6347