-
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
chore(deps): update dependency vitest to v2 #694
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-vitest-monorepo
base: main
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.
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
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/vitest@0.34.6 |
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
December 9, 2023 21:59
83811b9
to
c51f0ff
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
December 19, 2023 16:45
c51f0ff
to
529dc67
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
January 5, 2024 09:52
3020a23
to
ba9125a
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
2 times, most recently
from
January 17, 2024 17:14
070facc
to
fb5c618
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
January 26, 2024 16:52
fb5c618
to
1ec6d0c
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
2 times, most recently
from
February 20, 2024 15:33
fc0a09d
to
2108ce1
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
March 15, 2024 14:47
2108ce1
to
0989418
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
April 11, 2024 18:25
0989418
to
93624cb
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
April 30, 2024 09:18
4a24330
to
bc36a40
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
May 3, 2024 16:06
bc36a40
to
e60574d
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 8, 2024 14:10
e60574d
to
7fb8657
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1
chore(deps): update dependency vitest to v2
Jul 8, 2024
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
July 15, 2024 12:02
a12fb4d
to
683df79
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 22, 2024 14:17
683df79
to
2cfd588
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 31, 2024 14:09
2cfd588
to
0360be0
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
September 12, 2024 17:23
0360be0
to
2d4383b
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
September 13, 2024 17:21
2d4383b
to
7c6a2f7
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.
This PR contains the following updates:
0.34.6
->2.1.1
Release Notes
vitest-dev/vitest (vitest)
v2.1.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.0
Compare Source
This release makes another big change to the Browser Mode by introducing locators API:
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
.🚀 Features
userEvent.upload
in playwright provider - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)--inspect
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)--inspect-brk
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)--exclude-after-remap
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6309 (5932a){ spy: true }
instead of a factory - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6289 (95f02)vi.advanceTimersToNextFrame
- by @bnjm and @sheremet-va in https://github.com/vitest-dev/vitest/issues/6347 (8ff63)🐞 Bug Fixes
index
file - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6266 (081cf)expect.getState().testPath
always returns correct path - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6472 (ac698)vitest
and@vitest/*
versions don't match - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6317 (e662c)vitenode
for uncovered files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6044 (da52d)performance.now
instead ofDate.now
for duration - by @LuciNyan in https://github.com/vitest-dev/vitest/issues/6382 (fe489)toMatchInlineSnapshot
updates at the same location - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6332 (1606f)typecheck.include
overlaps withinclude
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6256 (153ff)View changes on GitHub
v2.0.5
Compare Source
🚀 Features
🐞 Bug Fixes
testNamePattern
adds leading space - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6186 (073a5)afterEach
cleanup hooks in node entrypoint - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6192 (e6fbc)defineProject
anddefineWorkspace
types - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6198 (8cd82)node:*
imports in__mocks__
folder - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6204 (a48be)View changes on GitHub
v2.0.4
Compare Source
🐞 Bug Fixes
require
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6159 (807a2)*.cts
files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6189 (5da45)thresholds.<glob>.100
option - by @thor-juhasz and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6174 (f6845)mockImplementation
for function overload and unions - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6181 (7a75b)View changes on GitHub
v2.0.3
Compare Source
🚀 Features
🐞 Bug Fixes
--inspect-brk
stop on Windows - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6110 (f8519)vi.spyOn
toMockInstance
of function overload - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6086 (e9f9a)View changes on GitHub
v2.0.2
Compare Source
v2.0.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.0.0
Compare 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)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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/5047 (7f8f9)threads
pool: https://vitest.dev/guide/improving-performance.html#pool--merge-reports
to 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 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 https://github.com/vitest-dev/vitest/issues/5802 (dd754)indexScripts
toorchestratorScripts
in the browser config - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5842 (49f34)pool
API - now requirescollectTests
method alongsiderunTests
.🚀 Features
--output-json
- by @Joristdh in https://github.com/vitest-dev/vitest/issues/5745 (0766b)parseAst
,parseAstAsync
from vite - by @sheremet-va (f645e)click
event - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5777 (839c3)page.screenshot
method - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5853 (81c42)userEvent
methods, addfill
anddragAndDrop
events - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5882 (4dbea)expect.dom
method and bundlejest-dom
matchers with@vitest/browser
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5910 (3a96a)tripleClick
to 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
--exclude
option - by @fregante in https://github.com/vitest-dev/vitest/issues/5782 (d6700)project.provide
type - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5959 (0eda9)preview
provider when running in StackBlitz - by @userquin in https://github.com/vitest-dev/vitest/issues/5836 (76e13)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.