Skip to content

chore(deps): update dependency vitest to ^0.34.0#64

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo
Open

chore(deps): update dependency vitest to ^0.34.0#64
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 6, 2023

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^0.32.2^0.34.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

v0.34.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.34.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes
  • Transform mode affects only test files, not regular files  -  by @​sheremet-va in #​3491 (9608b)
    • transformMode is now moved to server.transformMode. This option is highly discouraged to use. If you need to change the transform mode, use the new option testTransformMode instead to control the mode based on the running test, not the current file path. By default, tests with jsdom or happy-dom use web transform mode, and tests using node or edge environment use ssr mode. If you have a custom environment, it should provide transformMode property.
  • Custom environment now should be processed before Vitest can consume it. It means that you cannot specify a path to a TS file or use import paths that should be processed by Vite.
  • Disable coverage.reportOnFailure by default  -  by @​AriPerkkio in #​3615 (0c6f6)
  • Remove @vitest/coverage-c8 package  -  by @​AriPerkkio in #​3614 (a90d6)
    • @vitest/coverage-c8 is no longer supported. Please, use @vitest/coverage-v8 instead.
  • Support running tests using VM context  -  by @​sheremet-va and @​dammy001 in #​3203 (b0929)
    • To address speed issues in some applications, Vitest now provides experimentalVmThreads pool to run your tests using VM Sandboxes environment. Make sure you understand all pitfalls of this pool before opening an issue.
  • Introduce server option  -  by @​fenghan34 and @​sheremet-va in #​3725 (dc4fa)
    • Most of deps. options are now moved to server.deps with a deprecation warning. Please, consider using deps.optimizer instead of deps.inline/deps.external. Ideally, we would like to move away from using server.deps.inline altogether.
  • vite-node: Make CLI arguments parsing behavior consistent with node/tsx/ts-node  -  by @​rxliuli in #​3574 (1cd4e)
    • You now have to provide CLI arguments before the entry point. For example, instead of vite-node index.ts --watch, you now have to do vite-node --watch index.ts.
  • Add preact example, remove optimizer experimental status, enable by default  -  by @​sheremet-va and @​eryue0220 in #​3854 (4b946)
    • deps.optimizer is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options from optimizeDeps and ssr.optimizeDeps which are populated by other plugins (like, Svelte).
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
  • Deprecate deps.registerNodeLoader  -  by @​sheremet-va (7f45b)
    • This option was introduced to support aliasing inside external packages. Please, use deps.optimizer.web instead. If you test Node.js applications, consider adding external packages to server.deps.inline.
    View changes on GitHub

v0.33.0

Compare Source

   🚨 Breaking Changes
  • Revert default include patterns  -  by @​so1ve #​3729
    • 0.32.0 changed the default include 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 78e7d55 to 1441b1c Compare July 10, 2023 08:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from e274631 to f1b6b65 Compare July 17, 2023 12:48
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from a01567c to 083c976 Compare July 31, 2023 03:47
@renovate 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 renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 9ff1684 to c2f8a18 Compare August 7, 2023 05:13
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c2f8a18 to b0326ec Compare August 14, 2023 04:52
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from d07b490 to 2840a50 Compare August 31, 2023 21:13
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 96e33ed to 6cc115d Compare September 6, 2023 01:01
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 337c2bd to 4bcd064 Compare February 29, 2024 17:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 1290ac4 to 002a259 Compare March 6, 2024 21:11
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 0bd9308 to d292d1c Compare March 18, 2024 21:37
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d292d1c to 92c4fd7 Compare March 19, 2024 19:54
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 42cc397 to aad19a9 Compare May 6, 2024 19:19
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from aad19a9 to 16a4161 Compare May 8, 2024 17:44
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 16a4161 to 5614757 Compare June 4, 2024 04:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from b3c1545 to ebfc66c Compare June 22, 2024 12:42
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from ebfc66c to ceadfd3 Compare July 2, 2024 00:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 1bf8f48 to 6e7551b Compare August 9, 2024 22:01
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6e7551b to 1207195 Compare August 19, 2024 08:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 1fc0a4b to 0fb8d24 Compare September 1, 2024 15:40
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 8c11823 to 0413b85 Compare September 9, 2024 19:49
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 01ebf63 to de80bba Compare September 16, 2024 22:34
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from d5f72a5 to 2a712dd Compare September 28, 2024 01:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from bbfc9bc to b5f9fea Compare October 9, 2024 03:49
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b5f9fea to 514af2c Compare October 17, 2024 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants