Update dependency vitest to v0.29.3 - autoclosed (!701) · Merge requests · Water Mission Area / Internet of Water / waterdataui

igswsihw-wmadepbot requested to merge renovate/vitest-0.x into main Jan 22, 2023

This MR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vitest	`0.28.4` -> `0.29.3`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the logs for more information.

Release Notes

vitest-dev/vitest

`v0.29.3`

Compare Source

🚀 Features

Use custom colors implementation instead of picocolors - by @sheremet-va (427b0)
Uncaught errors to indicate env teardown - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2982 (1fe82)
config: Add an option to run setupFiles in sequence - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3008 (c2e25)

🐞 Bug Fixes

Wait for optimized dependency to be bundled in non-pnpm package managers - by @sheremet-va (d2460)

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 in child_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 (like process.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 https://github.com/vitest-dev/vitest/issues/2836 (94247)
Coverage-c8 to use V8 profiler directly instead of NODE_V8_COVERAGE - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)
Add a link to the comment at the top of the snapshot file - by @btea in https://github.com/vitest-dev/vitest/issues/2867 (615e1)
Always run separate environments in isolation - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2860 (1f858)
- Tests with node and jsdom (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 https://github.com/vitest-dev/vitest/issues/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.