-
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
Update dependency vitest to v2 #59
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.
Open
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
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
December 9, 2023 21:47
a352fa0
to
4a25a22
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
December 19, 2023 17:05
4a25a22
to
7a704a5
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
January 5, 2024 11:12
f9129e8
to
5df93ac
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
2 times, most recently
from
January 17, 2024 20:16
be354c1
to
af1c03a
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
January 26, 2024 19:00
af1c03a
to
86f5af9
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
2 times, most recently
from
February 20, 2024 15:09
20c4380
to
32d30f2
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
March 15, 2024 12:20
32d30f2
to
bd30878
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
April 11, 2024 19:33
bd30878
to
b6392a4
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
3 times, most recently
from
April 30, 2024 10:58
2942abe
to
9330c4d
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
May 3, 2024 18:51
9330c4d
to
ecb9bda
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 8, 2024 12:12
ecb9bda
to
5de3909
Compare
renovate
bot
changed the title
Update dependency vitest to v1
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 10:23
9689986
to
647c7c8
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 22, 2024 14:10
647c7c8
to
243a0c6
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
July 31, 2024 14:17
243a0c6
to
44d38b5
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
2 times, most recently
from
September 13, 2024 16:30
86c6789
to
977b0f5
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
October 2, 2024 18:36
977b0f5
to
90f8537
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
October 14, 2024 20:13
90f8537
to
e226b33
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
October 28, 2024 14:49
e226b33
to
7055246
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.22.1
->2.1.4
Release Notes
vitest-dev/vitest (vitest)
v2.1.4
Compare Source
🚀 Features
transformIndexHtml
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6725 (16902)🐞 Bug Fixes
v=
queries to setup files imports - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6759 (b8258)toThrowError
with empty string parameter - by @shulaoda in https://github.com/vitest-dev/vitest/issues/6710 (a6129)test.extend
type exports - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6707 (e5c38)🏎 Performance
hash
to replacecreateHash
- by @btea in https://github.com/vitest-dev/vitest/issues/6703 (5d07b)View changes on GitHub
v2.1.3
Compare Source
🐞 Bug Fixes
toBeNaN, toBeUndefined, toBeNull, toBeTruthy, toBeFalsy
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6697 (e0027)/mockServiceWorker.js
instead of/__vitest_msw__
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6687 (4b2ce)toMatchObject
diff - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6620 (d289e)<empty line>
logs when interleavingconsole.log/error
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6644 (9ece3)fast-glob
instead oftinyglobby
in Vitest - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6688 (70baa)🏎 Performance
View changes on GitHub
v2.1.2
Compare Source
🐞 Bug Fixes
Vitest.setServer
to postconfigureServer
hook to enable import analysis for workspace config loading - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6584 (e7f35)BenchmarkResult.samples
array to reduce memory usage - by @hi-ogawa and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6541 (a6407)data:
protocol on preview provider file upload - by @userquin in https://github.com/vitest-dev/vitest/issues/6501 (e9821)*.astro
by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6565 (f8ff7)cleanOnRerun: false
to invalidate previous results - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6592 (88bde)toBeDefined
withexpect.poll
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6562 (f7da6)beforeAll
failed - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6524 (fb797)onTestFinished
andonTestFailed
duringretry
andrepeats
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6609 (c5e29)--standalone
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6577 (d0bf8)View changes on GitHub
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)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 becomes conflicted, 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.