Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2022

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 0.23.4 -> 0.34.6 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

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in #​3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in #​3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in #​3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in #​3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes

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 force-pushed the renovate/vitest-monorepo branch from 287df9d to 878f575 Compare October 31, 2022 13:23
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.24.3 chore(deps): update dependency vitest to v0.24.4 Oct 31, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 878f575 to ba41318 Compare November 1, 2022 19:42
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.24.4 chore(deps): update dependency vitest to v0.24.5 Nov 1, 2022
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.24.5 chore(deps): update dependency vitest to v0.25.0 Nov 7, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 1818e18 to b9d437a Compare November 8, 2022 17:03
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.0 chore(deps): update dependency vitest to v0.25.1 Nov 8, 2022
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.1 chore(deps): update dependency vitest to v0.25.2 Nov 14, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b9d437a to 2de617a Compare November 14, 2022 16:56
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2de617a to 1538a80 Compare November 22, 2022 13:56
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.2 chore(deps): update dependency vitest to v0.25.3 Nov 22, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1538a80 to 45e18a9 Compare December 5, 2022 18:58
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.3 chore(deps): update dependency vitest to v0.25.4 Dec 5, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 45e18a9 to e7b4522 Compare December 6, 2022 20:25
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.4 chore(deps): update dependency vitest to v0.25.5 Dec 6, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e7b4522 to 33e83e6 Compare December 8, 2022 15:04
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.5 chore(deps): update dependency vitest to v0.25.6 Dec 8, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 33e83e6 to b233715 Compare December 10, 2022 21:30
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.6 chore(deps): update dependency vitest to v0.25.7 Dec 10, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b233715 to b320c47 Compare December 13, 2022 12:49
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.7 chore(deps): update dependency vitest to v0.25.8 Dec 13, 2022
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.8 Update dependency vitest to v0.25.8 Dec 17, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.25.8 chore(deps): update dependency vitest to v0.25.8 Dec 17, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b320c47 to b24f7d8 Compare December 19, 2022 12:50
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.25.8 chore(deps): update dependency vitest to v0.26.0 Dec 19, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b24f7d8 to 070b799 Compare December 20, 2022 13:17
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.26.0 chore(deps): update dependency vitest to v0.26.1 Dec 20, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 070b799 to 6881ca3 Compare December 21, 2022 13:33
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.26.1 chore(deps): update dependency vitest to v0.26.2 Dec 21, 2022
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.4 chore(deps): update dependency vitest to v0.33.0 Jul 6, 2023
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.33.0 chore(deps): update dependency vitest to v0.34.1 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 66b04e3 to edb6082 Compare August 1, 2023 17:11
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.1 chore(deps): update dependency vitest to v0.34.2 Aug 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from edb6082 to 12fc6fd Compare August 17, 2023 10:36
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 12fc6fd to 43ec2fb Compare August 25, 2023 08:48
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.2 chore(deps): update dependency vitest to v0.34.3 Aug 25, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 43ec2fb to 0744f2e Compare September 8, 2023 11:35
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.3 chore(deps): update dependency vitest to v0.34.4 Sep 8, 2023
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.4 chore(deps): update dependency vitest to v0.34.5 Sep 21, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0744f2e to f504461 Compare September 21, 2023 14:36
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f504461 to 2620a65 Compare September 29, 2023 15:27
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.5 chore(deps): update dependency vitest to v0.34.6 Sep 29, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2620a65 to e3da398 Compare January 21, 2024 03:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e3da398 to 26af539 Compare March 29, 2024 18:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 26af539 to 50291d7 Compare October 6, 2024 12:38
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.6 chore(deps): update dependency vitest to v0.34.6 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/vitest-monorepo branch December 8, 2024 18:37
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.6 - autoclosed chore(deps): update dependency vitest to v0.34.6 Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 08c9177 to 4f7c1d7 Compare August 13, 2025 17:30
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4f7c1d7 to fa9149d Compare August 19, 2025 17:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fa9149d to e59bd0a Compare August 31, 2025 11:16
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e59bd0a to 47bf4a8 Compare September 25, 2025 16:11
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 47bf4a8 to 7533dcb Compare October 22, 2025 00:37
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7533dcb to 83dc557 Compare November 10, 2025 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant