This repository has been archived by the owner on Dec 3, 2023. It is now read-only.
chore(deps): update dependency vitest to v0.31.0 #204
Merged
Merged
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
Open in CodeSandbox Web Editor | VS Code | VS Code Insiders |
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 21, 2022 11:54
39fea88
to
f9b8063
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.26.1
chore(deps): update dependency vitest to v0.26.2
Dec 21, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 1, 2023 15:21
f9b8063
to
f7b30fe
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.26.2
chore(deps): update dependency vitest to v0.26.3
Jan 1, 2023
PR Summary
|
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 9, 2023 15:24
f7b30fe
to
0001367
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.26.3
chore(deps): update dependency vitest to v0.27.0
Jan 9, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 11, 2023 19:48
0001367
to
f78e70b
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.27.0
chore(deps): update dependency vitest to v0.27.1
Jan 11, 2023
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.27.1
chore(deps): update dependency vitest to v0.27.2
Jan 17, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
January 21, 2023 18:21
a177830
to
be42aa6
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.27.2
chore(deps): update dependency vitest to v0.27.3
Jan 21, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 23, 2023 09:38
be42aa6
to
a6b4534
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.27.3
chore(deps): update dependency vitest to v0.28.0
Jan 23, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 23, 2023 13:30
a6b4534
to
a7e1f27
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.0
chore(deps): update dependency vitest to v0.28.1
Jan 23, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 25, 2023 13:46
a7e1f27
to
95b6b43
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.1
chore(deps): update dependency vitest to v0.28.2
Jan 25, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 27, 2023 13:13
95b6b43
to
b627c79
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.2
chore(deps): update dependency vitest to v0.28.3
Jan 27, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 3, 2023 13:44
b627c79
to
d333785
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.3
chore(deps): update dependency vitest to v0.28.4
Feb 3, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 5, 2023 02:31
d333785
to
1039e07
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 13, 2023 17:38
1039e07
to
ca66476
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.4
chore(deps): update dependency vitest to v0.28.5
Feb 13, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 25, 2023 11:22
ca66476
to
d75425f
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.28.5
chore(deps): update dependency vitest to v0.29.1
Feb 25, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 28, 2023 17:36
d75425f
to
3817203
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.1
chore(deps): update dependency vitest to v0.29.2
Feb 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 15, 2023 20:34
3817203
to
c6f3877
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.2
chore(deps): update dependency vitest to v0.29.3
Mar 15, 2023
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.3
chore(deps): update dependency vitest to v0.29.5
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 20, 2023 17:27
c6f3877
to
60c01dc
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.5
chore(deps): update dependency vitest to v0.29.7
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 20, 2023 20:57
60c01dc
to
74711f3
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 28, 2023 18:49
74711f3
to
b84f1d8
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.7
chore(deps): update dependency vitest to v0.29.8
Mar 29, 2023
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.8
chore(deps): update dependency vitest to v0.30.1
Apr 17, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 17, 2023 12:08
b84f1d8
to
cc5cf52
Compare
PR Summary
|
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 4, 2023 05:55
cc5cf52
to
03d4ac2
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.30.1
chore(deps): update dependency vitest to v0.31.0
May 4, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
9 times, most recently
from
May 4, 2023 06:52
4d7f8f3
to
c533104
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 4, 2023 06:53
c533104
to
ed16336
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 4, 2023 06:54
ed16336
to
7fcf234
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.26.0
->0.31.0
Release Notes
vitest-dev/vitest
v0.31.0
Compare Source
🚨 Breaking Changes
Update mock implementation to support ESM runtime, introduce "vi.hoisted" - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3258 (0c09a)
vi.hoisted
to run code before imports are executed:You can also use it to pass variables to
vi.mock
:Move assertion declarations to expect package - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)
🚀 Features
--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
🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.28.4
Compare Source
🐞 Bug Fixes
onWatcherStart
whentypecheck.ignoreSourceErrors
is true - by @mascii and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2774 (d612e)View changes on GitHub
v0.28.3
Compare Source
🚀 Features
config
option to be false - by @antfu in https://github.com/vitest-dev/vitest/issues/2749 (c66e3)🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.28.2
Compare Source
🐞 Bug Fixes
timestamp: 0
- by @danielroe in https://github.com/vitest-dev/vitest/issues/2747 (e88c0)View changes on GitHub
v0.28.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.28.0
Compare Source
🚨 Breaking Changes
@vitet/runner
package instead ofvitest
🐞 Bug Fixes
View changes on GitHub
v0.27.3
Compare Source
🚀 Features
environmentMatchGlobs
option to auto infer env based on glob - by @antfu in https://github.com/vitest-dev/vitest/issues/2714 (3e142)🐞 Bug Fixes
reportCoverage
context can be optional - by @antfu (4cd1e)View changes on GitHub
v0.27.2
Compare Source
🚀 Features
🐞 Bug Fixes
coverage.all
only when all tests are run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2665 (85096)🏎 Performance
View changes on GitHub
v0.27.1
Compare Source
🚀 Features
🐞 Bug Fixes
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.