This repository has been archived by the owner on Jun 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Update dependency vitest to v0.32.0 #225
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/vitest-monorepo
base: master
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/vitest-monorepo
branch
2 times, most recently
from
October 31, 2022 11:44
caee37c
to
9a48c8d
Compare
renovate
bot
changed the title
Update dependency vitest to v0.24.3
Update dependency vitest to v0.24.4
Oct 31, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
November 1, 2022 19:29
8ba00f0
to
394f6d2
Compare
renovate
bot
changed the title
Update dependency vitest to v0.24.4
Update dependency vitest to v0.24.5
Nov 1, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
November 7, 2022 18:25
c722533
to
ca4debf
Compare
renovate
bot
changed the title
Update dependency vitest to v0.24.5
Update dependency vitest to v0.25.0
Nov 7, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 8, 2022 18:57
0c6c307
to
6105640
Compare
renovate
bot
changed the title
Update dependency vitest to v0.25.0
Update dependency vitest to v0.25.1
Nov 8, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
November 14, 2022 16:56
6105640
to
84751f7
Compare
renovate
bot
changed the title
Update dependency vitest to v0.25.1
Update dependency vitest to v0.25.2
Nov 14, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
November 16, 2022 13:42
5c204db
to
80f8772
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 22, 2022 15:47
f7340f2
to
ebc9380
Compare
renovate
bot
changed the title
Update dependency vitest to v0.25.2
Update dependency vitest to v0.25.3
Nov 22, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
December 1, 2022 01:09
9fc5dcb
to
f2990cf
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 5, 2022 20:54
f2990cf
to
b258ca0
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
February 17, 2023 10:52
85187fe
to
b80ab8e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 25, 2023 10:07
b80ab8e
to
b76d16b
Compare
renovate
bot
changed the title
Update dependency vitest to v0.28.5
Update dependency vitest to v0.29.1
Feb 25, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 28, 2023 16:36
b76d16b
to
fb8104a
Compare
renovate
bot
changed the title
Update dependency vitest to v0.29.1
Update dependency vitest to v0.29.2
Feb 28, 2023
renovate
bot
changed the title
Update dependency vitest to v0.29.2
Update dependency vitest to v0.29.3
Mar 15, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 15, 2023 20:36
fb8104a
to
9223cfa
Compare
renovate
bot
changed the title
Update dependency vitest to v0.29.3
Update dependency vitest to v0.29.5
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 20, 2023 15:27
9223cfa
to
67df8dc
Compare
renovate
bot
changed the title
Update dependency vitest to v0.29.5
Update dependency vitest to v0.29.7
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 20, 2023 22:23
67df8dc
to
4193422
Compare
renovate
bot
changed the title
Update dependency vitest to v0.29.7
Update dependency vitest to v0.29.8
Mar 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 28, 2023 18:24
4193422
to
f117b04
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 9, 2023 16:32
f117b04
to
4d1dca6
Compare
renovate
bot
changed the title
Update dependency vitest to v0.29.8
Update dependency vitest to v0.30.0
Apr 9, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 11, 2023 15:46
4d1dca6
to
f0b6b5a
Compare
renovate
bot
changed the title
Update dependency vitest to v0.30.0
Update dependency vitest to v0.30.1
Apr 11, 2023
renovate
bot
changed the title
Update dependency vitest to v0.30.1
Update dependency vitest to v0.31.1
May 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 28, 2023 09:27
f0b6b5a
to
75c75d8
Compare
renovate
bot
changed the title
Update dependency vitest to v0.31.1
Update dependency vitest to v0.31.2
May 30, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
May 31, 2023 15:23
fae6fc9
to
15cc4e3
Compare
renovate
bot
changed the title
Update dependency vitest to v0.31.2
Update dependency vitest to v0.31.3
May 31, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 2, 2023 17:49
15cc4e3
to
e4dcb6a
Compare
renovate
bot
changed the title
Update dependency vitest to v0.31.3
Update dependency vitest to v0.31.4
Jun 2, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 6, 2023 19:37
e4dcb6a
to
71a406f
Compare
renovate
bot
changed the title
Update dependency vitest to v0.31.4
Update dependency vitest to v0.32.0
Jun 6, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.23.4
->0.32.0
Release Notes
vitest-dev/vitest
v0.32.0
Compare Source
🚨 Breaking Changes
test.js
to be a test file. Also any file in__tests__
is now considered to be a test, not just files withtest
orspec
suffix.@vitest/coverage-v8
package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)@vitest/coverage-c8
is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user hasc8
as their coverage provider. Please, install the new@vitest/coverage-v8
package if you previously used@vitest/coverage-c8
.spy.mockRestore
on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.🚀 Features
expect.soft
- by @Dunqing in https://github.com/vitest-dev/vitest/issues/3507 (7c687)describe
/test
name - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3497 (15253)🐞 Bug Fixes
View changes on GitHub
v0.31.4
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.31.3
Compare Source
🚀 Features
VITE_NODE_DEPS_MODULE_DIRECTORIES
from .npmrc - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3471 (393bf)🐞 Bug Fixes
View changes on GitHub
v0.31.2
Compare Source
🚀 Features
test.each
ordescribe.each
- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3360 (7c2f7)reportOnFailure
option - by @AriPerkkio and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3453 (1988f)🐞 Bug Fixes
SIGINT
is received - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3407 (a2cc2)rejects
&resolves
breaks with thenable objects - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3456 (4e996)birpc
timeouts whenMath.random
mock is not restored - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3460 (cd5d5)less
extension - by @rluvaton in https://github.com/vitest-dev/vitest/issues/3465 (4d045)PartialMock
with async TReturns - by @ghry5 in https://github.com/vitest-dev/vitest/issues/3462 (b664d)View changes on GitHub
v0.31.1
Compare Source
🚀 Features
r
should rerun current pattern tests - by @Dunqing and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3305 (69d27)🐞 Bug Fixes
cwd
from test name filter - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3353 (324a9)toMatchInlineSnapshot
fails when file path includes parentheses - by @pacexy in https://github.com/vitest-dev/vitest/issues/3370 and https://github.com/vitest-dev/vitest/issues/3371 (dcf13)View changes on GitHub
v0.31.0
Compare Source
🚨 Breaking Changes
Remove
browser
from allowed pools insidepoolMatchGlob
config option. Please, use Vitest workspaces for running tests in the browser.Move assertion declarations to expect package - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)
🚀 Features
vi.hoisted
to run code before imports are executed:vi.mock
:--bail
option for cancelling test run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3163 (8d460)🐞 Bug Fixes
thresholdAutoUpdate
to work withperFile
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3182 (29eeb)import.meta.hot.send
mock - by @antfu (b1624)View changes on GitHub
v0.30.1
Compare Source
🐞 Bug Fixes
performance
andAggregateError
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3171 (cce45)test.each
respectschaiConfig
- by @sheremet-va (4f6c1)toMatchFileSnapshot
ensure dir exists - by @antfu in https://github.com/vitest-dev/vitest/issues/3155 (31168)skipWriting
check - by @antfu (5436c)toMatchFileSnapshot
- by @antfu in https://github.com/vitest-dev/vitest/issues/3164 (df3f2)View changes on GitHub
v0.30.0
Compare Source
🚨 Breaking Changes
🚀 Features
toMatchFileSnapshot
and auto queuing expect promise - by @antfu in https://github.com/vitest-dev/vitest/issues/3116 (bdc06)🐞 Bug Fixes
View changes on GitHub
v0.29.8
Compare Source
🚀 Features
istanbul
coverage support for browser testing - by @sheremet-va and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3040 (0f44d)🐞 Bug Fixes
View changes on GitHub
v0.29.7
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.6
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.5
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.4
Compare Source
🚀 Features
--test-timeout
CLI argument - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3019 (63c62)🐞 Bug Fixes
View changes on GitHub
v0.29.3
Compare Source
🚀 Features
🐞 Bug Fixes
any
as default value for TArgs in vi.fn() - by @jessevanassen in https://github.com/vitest-dev/vitest/issues/2947 (1bdcc)🏎 Performance
View changes on GitHub
v0.29.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.0
Compare Source
This release makes some significant changes to how tests are running. If you were using
--no-threads
before, you might consider enabling--single-thread
instead (because your tests are now running inchild_process
instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (likeprocess.chdir()
, you can now use this option.One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with
--no-isolate
,--no-threads
or--single-thread
- you might need to update your setup files if you were relying on a global variable before.If you had performance issues on large code bases before, try the new
deps.experimentalOptimizer
option instead of disabling threads. Feedback is welcome!One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
🚨 Breaking Changes
NODE_V8_COVERAGE
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)node
andjsdom
(and other environments) now don't share the same global scope, if you run them with--no-isolate
or--no-threads
flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.28.5
[Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.28.4...v0.28
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.