Skip to content

Update dependency vitest to ^0.34.0#19

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

Update dependency vitest to ^0.34.0#19
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 26, 2022

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

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 - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 fe0a7fc to f84c53a Compare January 9, 2023 14:19
@renovate renovate bot changed the title Update dependency vitest to ^0.26.0 Update dependency vitest to ^0.27.0 Jan 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f84c53a to d7af584 Compare March 16, 2023 07:33
@renovate renovate bot changed the title Update dependency vitest to ^0.27.0 Update dependency vitest to ^0.29.0 Mar 16, 2023
@renovate renovate bot changed the title Update dependency vitest to ^0.29.0 Update dependency vitest to ^0.30.0 Apr 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d7af584 to c7b0968 Compare April 17, 2023 11:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c7b0968 to 371d485 Compare May 28, 2023 12:10
@renovate renovate bot changed the title Update dependency vitest to ^0.30.0 Update dependency vitest to ^0.31.0 May 28, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 371d485 to a837291 Compare June 6, 2023 20:05
@renovate renovate bot changed the title Update dependency vitest to ^0.31.0 Update dependency vitest to ^0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a837291 to 323c815 Compare July 6, 2023 18:10
@renovate renovate bot changed the title Update dependency vitest to ^0.32.0 Update dependency vitest to ^0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 323c815 to ee25687 Compare August 1, 2023 18:35
@renovate renovate bot changed the title Update dependency vitest to ^0.33.0 Update dependency vitest to ^0.34.0 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from b27ccc8 to 4316d43 Compare August 13, 2025 17:06
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4316d43 to db1981b Compare August 19, 2025 14:43
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from db1981b to 8a90cc9 Compare August 31, 2025 14:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8a90cc9 to a44f656 Compare September 25, 2025 16:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a44f656 to 4f3a3ff Compare October 21, 2025 17:46
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4f3a3ff to a05755d Compare November 10, 2025 18:58
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a05755d to 7df986b Compare November 19, 2025 00:13
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7df986b to c1c9f34 Compare December 3, 2025 18:30
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c1c9f34 to 94af839 Compare December 31, 2025 16:32
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 94af839 to e63a014 Compare January 8, 2026 19:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 4014158 to b42cf88 Compare January 23, 2026 17:58
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b42cf88 to 3d052c7 Compare February 2, 2026 20:00
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3d052c7 to 481e32f Compare February 12, 2026 18:09
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 481e32f to 69912ca Compare March 5, 2026 17:47
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.

0 participants