alices-wonderland / white-rabbit

0 stars 0 forks source link

chore(deps): update vitest monorepo to ^0.29.0 - autoclosed #49

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 ^0.28.5 -> ^0.29.0 age adoption passing confidence
vitest ^0.28.5 -> ^0.29.0 age adoption passing confidence

Release Notes

vitest-dev/vitest ### [`v0.29.1`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.29.1) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.29.0...v0.29.1) #####    🐞 Bug Fixes - Wait for optimized dependency to be bundled in non-pnpm package managers  -  by [@​sheremet-va](https://togithub.com/sheremet-va) [(d2460)](https://togithub.com/vitest-dev/vitest/commit/d2460b7a) #####     [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.29.0...v0.29.1) ### [`v0.29.0`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.29.0) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.28.5...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 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`](https://vitest.dev/config/#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](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2836](https://togithub.com/vitest-dev/vitest/issues/2836) [(94247)](https://togithub.com/vitest-dev/vitest/commit/94247f1b) - Coverage-c8 to use V8 profiler directly instead of `NODE_V8_COVERAGE`  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2786](https://togithub.com/vitest-dev/vitest/issues/2786) [(095c6)](https://togithub.com/vitest-dev/vitest/commit/095c6390) - Add a link to the comment at the top of the snapshot file  -  by [@​btea](https://togithub.com/btea) in [https://github.com/vitest-dev/vitest/issues/2867](https://togithub.com/vitest-dev/vitest/issues/2867) [(615e1)](https://togithub.com/vitest-dev/vitest/commit/615e150b) - Always run separate environments in isolation  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2860](https://togithub.com/vitest-dev/vitest/issues/2860) [(1f858)](https://togithub.com/vitest-dev/vitest/commit/1f858e0c) - 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](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2772](https://togithub.com/vitest-dev/vitest/issues/2772) [(7bf54)](https://togithub.com/vitest-dev/vitest/commit/7bf54505) - 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](https://togithub.com/btkostner) in [https://github.com/vitest-dev/vitest/issues/2877](https://togithub.com/vitest-dev/vitest/issues/2877) [(bdb39)](https://togithub.com/vitest-dev/vitest/commit/bdb39569) - Use custom source-map-support implementation  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2905](https://togithub.com/vitest-dev/vitest/issues/2905) [(6ff6c)](https://togithub.com/vitest-dev/vitest/commit/6ff6c6eb) - Add an option to enable Vite optimizer  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2912](https://togithub.com/vitest-dev/vitest/issues/2912) [(af8de)](https://togithub.com/vitest-dev/vitest/commit/af8de362) - **coverage**: - Add support for coverage reporter options  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2690](https://togithub.com/vitest-dev/vitest/issues/2690) [(f8176)](https://togithub.com/vitest-dev/vitest/commit/f8176182) - Automatic threshold updating  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2886](https://togithub.com/vitest-dev/vitest/issues/2886) [(e1652)](https://togithub.com/vitest-dev/vitest/commit/e1652163) - **spy**: - Implement mock.withImplementation API  -  by [@​obadakhalili](https://togithub.com/obadakhalili) and [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2835](https://togithub.com/vitest-dev/vitest/issues/2835) [(610b1)](https://togithub.com/vitest-dev/vitest/commit/610b1d46) - **vite-node**: - Cli option for vite mode  -  by [@​abarke](https://togithub.com/abarke) in [https://github.com/vitest-dev/vitest/issues/2893](https://togithub.com/vitest-dev/vitest/issues/2893) [(0fc08)](https://togithub.com/vitest-dev/vitest/commit/0fc08032) #####    🐞 Bug Fixes - Wait for console.log to print a message before terminating a worker  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/2861](https://togithub.com/vitest-dev/vitest/issues/2861) [(fbc54)](https://togithub.com/vitest-dev/vitest/commit/fbc54c91) - Cleanup last mocked cache when call vi.doMock  -  by [@​mysteryven](https://togithub.com/mysteryven) in [https://github.com/vitest-dev/vitest/issues/2872](https://togithub.com/vitest-dev/vitest/issues/2872) [(65d71)](https://togithub.com/vitest-dev/vitest/commit/65d71b9e) - Reload changed configuration file on watch mode  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2889](https://togithub.com/vitest-dev/vitest/issues/2889) [(4d277)](https://togithub.com/vitest-dev/vitest/commit/4d277d8d) - **coverage**: Custom providers to work inside worker threads  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/2817](https://togithub.com/vitest-dev/vitest/issues/2817) [(81604)](https://togithub.com/vitest-dev/vitest/commit/81604bce) #####     [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.28.5...v0.29.0)

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), 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 these updates again.



This PR has been generated by Mend Renovate. View repository job log here.

codecov[bot] commented 1 year ago

Codecov Report

Merging #49 (34d8e61) into develop (c6d5930) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #49   +/-   ##
========================================
  Coverage    71.76%   71.76%           
========================================
  Files           41       41           
  Lines         4155     4155           
========================================
  Hits          2982     2982           
  Misses        1173     1173           
Flag Coverage Δ
backend 71.76% <ø> (ø)
unittests 71.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more