Bump vitest from 0.29.2 to 0.29.3
Created by: dependabot[bot]
Bumps vitest from 0.29.2 to 0.29.3.
Release notes
Sourced from vitest's releases.
v0.29.3
🚀 Features
- Use custom colors implementation instead of picocolors - by
@sheremet-va
(427b0)- Uncaught errors to indicate env teardown - by
@AriPerkkio
in vitest-dev/vitest#2982 (1fe82)- config: Add an option to run setupFiles in sequence - by
@sheremet-va
in vitest-dev/vitest#3008 (c2e25)
🐞 Bug Fixes
- Console log not visible - by
@AriPerkkio
in vitest-dev/vitest#2943 (02808)- Remove duplicate execArgv when deps.registerNodeLoader: true - by
@AriPerkkio
in vitest-dev/vitest#2965 (a1954)- Prevent running test cases timers after environment teardown - by
@AriPerkkio
in vitest-dev/vitest#2971 (bde75)- Don't mark setupFiles as test files, if experimentaOptimizer is used - by
@sheremet-va
in vitest-dev/vitest#2974 (819c6)- Config errors not visible - by
@AriPerkkio
in vitest-dev/vitest#2995 (f01c7)- --inspect to work inside workers - by
@AriPerkkio
in vitest-dev/vitest#2983 (36087)- types: Use
any
as default value for TArgs in vi.fn() - by@jessevanassen
in vitest-dev/vitest#2947 (1bdcc)
🏎 Performance
- reporters: Overall improvements - by
@AriPerkkio
in vitest-dev/vitest#3006 (22ca0)View changes on GitHub
Commits
-
d4d0425
chore: release v0.29.3 -
36087d1
fix: --inspect to work inside workers (#2983) -
c2e25bb
feat(config): add an option to run setupFiles in sequence (#3008) -
22ca0b6
perf(reporters): overall improvements (#3006) -
1fe8286
feat: uncaught errors to indicate env teardown (#2982) -
f01c783
fix: config errors not visible (#2995) -
427b062
feat: use custom colors implementation instead of picocolors -
819c6cb
fix: don't mark setupFiles as test files, if experimentaOptimizer is used (#2... -
bde75a3
fix: prevent running test cases timers after environment teardown (#2971) -
a1954cc
fix: remove duplicate execArgv when deps.registerNodeLoader: true (#2965) - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)