-
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 ^0.34.0 #13
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/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
Run & review this pull request in StackBlitz Codeflow. |
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
July 17, 2023 04:42
e0e0f80
to
848214b
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
July 31, 2023 03:06
5fae3ab
to
2cd79af
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to ^0.33.0
chore(deps): update dependency vitest to ^0.34.0
Aug 1, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
August 7, 2023 03:43
83cbc01
to
d9304ea
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 14, 2023 04:15
d9304ea
to
e74d481
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
September 4, 2023 03:04
3bba6ad
to
23fa208
Compare
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/vitest@0.32.4 |
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
September 18, 2023 03:20
85a906c
to
ffb7217
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
September 25, 2023 03:08
ffb7217
to
5853e7e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
October 23, 2023 03:06
0671455
to
b8011a2
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 6, 2023 03:43
63bd915
to
c7f381e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 20, 2023 03:08
4171254
to
a893e8d
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
November 27, 2023 03:13
a893e8d
to
80f1aef
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 4, 2023 03:46
80f1aef
to
4e17c3c
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 11, 2023 04:11
4e17c3c
to
f5a42f9
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 18, 2023 04:29
f5a42f9
to
8c0c28d
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 1, 2024 04:01
8c0c28d
to
25660e0
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
January 15, 2024 04:01
a987be7
to
730b9bd
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 22, 2024 04:23
730b9bd
to
ed819ef
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
February 5, 2024 03:45
2339a49
to
48904b5
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 12, 2024 03:14
48904b5
to
1141d19
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
February 25, 2024 12:07
b9acbba
to
ebed2bf
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
February 29, 2024 17:12
0d296a5
to
65296ec
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
March 13, 2024 16:16
c38fd40
to
d01deea
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
March 24, 2024 19:57
4d32aef
to
da711ee
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
April 3, 2024 01:26
a9d64e6
to
52bbd7c
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 5, 2024 00:07
52bbd7c
to
5f33bf5
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.32.0
->^0.34.0
Release Notes
vitest-dev/vitest (vitest)
v0.34.6
Compare Source
🐞 Bug Fixes
test.extend
should be init once time in all test - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4168 (730b2)View changes on GitHub
v0.34.5
Compare Source
🚀 Features
diff
option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4063 (b50cf)coverage['100']
to istanbul provider - by @marcelobotega in https://github.com/vitest-dev/vitest/issues/4109 (a7e09)vi.waitFor
method - by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4113 (d79cb)vi.waitUntil
method - by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4129 (e0ac9)🐞 Bug Fixes
toThrow
- by @Dunqing in https://github.com/vitest-dev/vitest/issues/3979 (725a0)testNamePattern
- by @segrey in https://github.com/vitest-dev/vitest/issues/4103 and https://github.com/vitest-dev/vitest/issues/4104 (3c305)test.extend
doesn't work in hooks without test - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4065 (175c7)SourceMapInput
to fix CYCLIC_CROSS_CHUNK_REEXPORT - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4128 (ca70a)🏎 Performance
View changes on GitHub
v0.34.4
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.34.3
Compare Source
🚀 Features
allowExternal
option - by @vojvodics and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3894 (c03fa)vitest/reporters
- by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3980 (5704b)🐞 Bug Fixes
View changes on GitHub
v0.34.2
Compare Source
🚀 Features
--experimental-vm-threads
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3880 (f4e6e)ctx.skip()
inside the running test - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3966 (5c88d)🐞 Bug Fixes
execute.d.ts
- by @btea in https://github.com/vitest-dev/vitest/issues/3970 (0f8e6)?inline
query is specified - by @thebanjomatic and Adam Hines in https://github.com/vitest-dev/vitest/issues/3952 (3891d)🏎 Performance
View changes on GitHub
v0.34.1
Compare Source
🐞 Bug Fixes
--experimental-vm-worker-memory-limit
totinypool
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)View changes on GitHub
v0.34.0
Compare Source
🚨 Breaking Changes
transformMode
is now moved toserver.transformMode
. This option is highly discouraged to use. If you need to change the transform mode, use the new optiontestTransformMode
instead to control the mode based on the running test, not the current file path. By default, tests withjsdom
orhappy-dom
useweb
transform mode, and tests usingnode
oredge
environment usessr
mode. If you have a custom environment, it should providetransformMode
property.coverage.reportOnFailure
by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)@vitest/coverage-c8
package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)@vitest/coverage-c8
is no longer supported. Please, use@vitest/coverage-v8
instead.experimentalVmThreads
pool to run your tests using VM Sandboxes environment. Make sure you understand all pitfalls of this pool before opening an issue.server
option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3725 (dc4fa)deps.
options are now moved toserver.deps
with a deprecation warning. Please, consider usingdeps.optimizer
instead ofdeps.inline
/deps.external
. Ideally, we would like to move away from usingserver.deps.inline
altogether.vite-node index.ts --watch
, you now have to dovite-node --watch index.ts
.deps.optimizer
is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options fromoptimizeDeps
andssr.optimizeDeps
which are populated by other plugins (like, Svelte).🚀 Features
describe.sequential
- by @fenghan34 and @dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)--related --watch
reruns non-affected tests if they were changed during a run - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)🐞 Bug Fixes
defineConfig
type from vite - by @sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)toStrictEqual
- by @Dunqing (52aef)istanbul-lib-instrument
to v6 to fix vulnerable dependency - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)🏎 Performance
deps.optimizer.web
instead. If you test Node.js applications, consider adding external packages toserver.deps.inline
.View changes on GitHub
v0.33.0
Compare Source
🚨 Breaking Changes
0.32.0
changed the defaultinclude
globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.🐞 Bug Fixes
View changes on GitHub
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.