chore(deps): update vitest to v0.29.7 - autoclosed #416
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.18.1
->0.29.7
Release Notes
vitest-dev/vitest
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
coverage.extension
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2641 (7e388)View changes on GitHub
v0.27.0
Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.26.3
Compare Source
🚀 Features
importOriginal
helper to the factory - by @antfu in https://github.com/vitest-dev/vitest/issues/2551 (853ee)🐞 Bug Fixes
View changes on GitHub
v0.26.2
Compare Source
🚀 Features
🐞 Bug Fixes
dir
- by @antfu in https://github.com/vitest-dev/vitest/issues/2550 (f6b59)View changes on GitHub
v0.26.1
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.26.0
Compare Source
🚨 Breaking Changes
node
, Vitest will not resolve invalid named exports (exports that are on "default" property will not magically appear as named exports), unlessdeps.interopDefault
is enabled, or dependency is indeps.inline
. This change doesn't affectjsdom
,happy-dom
oredge
environments.structuredClone
, if it's available, or fallbacks to a polyfill.SharedWorker
🚀 Features
@vitest/ui
installed, you can now use'html'
reporter to get a beautiful UI to view your test results, inspect module graph and read log messages.🐞 Bug Fixes
View changes on GitHub
v0.25.8
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.25.7
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.25.6
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.25.5
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.25.4
Compare Source
🚀 Features
each
title - by @scarf005 in https://github.com/vitest-dev/vitest/issues/2420 and https://github.com/vitest-dev/vitest/issues/2421 (1868f)🐞 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.