xicons
xicons copied to clipboard
build(deps-dev): bump vitest from 0.2.8 to 0.29.2 in /packages/v2icons-utils
Bumps vitest from 0.2.8 to 0.29.2.
Release notes
Sourced from vitest's releases.
v0.29.2
🐞 Bug Fixes
- Optimize dependencies in setup files - by
@sheremet-va
in vitest-dev/vitest#2935 (c169f)- coverage: C8 provider to work when isolate:false - by
@AriPerkkio
in vitest-dev/vitest#2929 (86538)View changes on GitHub
v0.29.1
🐞 Bug Fixes
- Wait for optimized dependency to be bundled in non-pnpm package managers - by
@sheremet-va
(d2460)View changes on GitHub
v0.29.0
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
- Vitest as peer dependency for coverage packages - by
@AriPerkkio
in vitest-dev/vitest#2836 (94247)- Coverage-c8 to use V8 profiler directly instead of
NODE_V8_COVERAGE
- by@AriPerkkio
in vitest-dev/vitest#2786 (095c6)- Add a link to the comment at the top of the snapshot file - by
@btea
in vitest-dev/vitest#2867 (615e1)- Always run separate environments in isolation - by
@sheremet-va
in vitest-dev/vitest#2860 (1f858)
- Tests with
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.- Use child_process when --no-threads is used - by
@sheremet-va
in vitest-dev/vitest#2772 (7bf54)
- Tests inside
chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.🚀 Features
- Add test seed to banner - by
@btkostner
in vitest-dev/vitest#2877 (bdb39)- Use custom source-map-support implementation - by
@sheremet-va
in vitest-dev/vitest#2905 (6ff6c)- Add an option to enable Vite optimizer - by
@sheremet-va
in vitest-dev/vitest#2912 (af8de)- coverage:
- Add support for coverage reporter options - by
@AriPerkkio
in vitest-dev/vitest#2690 (f8176)- Automatic threshold updating - by
@AriPerkkio
in vitest-dev/vitest#2886 (e1652)- spy:
- Implement mock.withImplementation API - by
@obadakhalili
and@sheremet-va
in vitest-dev/vitest#2835 (610b1)- vite-node:
- Cli option for vite mode - by
@abarke
in vitest-dev/vitest#2893 (0fc08)🐞 Bug Fixes
- Wait for console.log to print a message before terminating a worker - by
@sheremet-va
in vitest-dev/vitest#2861 (fbc54)
... (truncated)
Commits
bce5a9f
chore: release v0.29.2c169f98
fix: optimize dependencies in setup files (#2935)20c9993
chore: release v0.29.1965f32a
chore: release v0.29.07bf5450
feat!: use child_process when --no-threads is used (#2772)4d277d8
fix: reload changed configuration file on watch mode (#2889)e165216
feat(coverage): automatic threshold updating (#2886)615e150
feat: add a link to the comment at the top of the snapshot file (#2867)af8de36
feat: add an option to enable Vite optimizer (#2912)6ff6c6e
feat: use custom source-map-support implementation (#2905)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by oreanno, a new releaser for vitest since your current version.
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)