Skip to content

chore(deps): update dependency vitest to ^0.34.6#13

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2023

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^0.25.3^0.34.6 age adoption passing 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
  • Don't print

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 changed the title chore(deps): update dependency vitest to ^0.29.3 chore(deps): update dependency vitest to ^0.29.4 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8140c03 to 0dc72fd Compare March 20, 2023 14:10
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.4 chore(deps): update dependency vitest to ^0.29.5 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0dc72fd to 2b65a34 Compare March 20, 2023 15:18
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.5 chore(deps): update dependency vitest to ^0.29.6 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from f31e2a0 to 3a847d0 Compare March 20, 2023 22:44
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.6 chore(deps): update dependency vitest to ^0.29.7 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3a847d0 to e94909f Compare March 28, 2023 20:24
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.7 chore(deps): update dependency vitest to ^0.29.8 Mar 28, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e94909f to 810f0b0 Compare April 9, 2023 16:19
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.8 chore(deps): update dependency vitest to ^0.30.0 Apr 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 810f0b0 to 599d4c6 Compare April 11, 2023 12:41
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.30.0 chore(deps): update dependency vitest to ^0.30.1 Apr 11, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 599d4c6 to f727544 Compare May 3, 2023 20:17
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.30.1 chore(deps): update dependency vitest to ^0.31.0 May 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f727544 to 50eccfd Compare May 17, 2023 18:09
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.31.0 chore(deps): update dependency vitest to ^0.31.1 May 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 50eccfd to d3121ed Compare June 1, 2023 03:56
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.31.1 chore(deps): update dependency vitest to ^0.31.3 Jun 1, 2023
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.31.3 chore(deps): update dependency vitest to ^0.31.4 Jun 2, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d3121ed to 6502520 Compare June 2, 2023 08:15
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6502520 to d033363 Compare June 10, 2023 08:37
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.31.4 chore(deps): update dependency vitest to ^0.32.0 Jun 10, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d033363 to 2ef0179 Compare June 17, 2023 05:17
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.32.0 chore(deps): update dependency vitest to ^0.32.2 Jun 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2ef0179 to 3bc09fb Compare July 4, 2023 02:57
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.32.2 chore(deps): update dependency vitest to ^0.32.4 Jul 4, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3bc09fb to 394180e Compare July 7, 2023 20:49
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.32.4 chore(deps): update dependency vitest to ^0.33.0 Jul 7, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 394180e to 28b6a4d Compare August 2, 2023 05:23
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.33.0 chore(deps): update dependency vitest to ^0.34.1 Aug 2, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 28b6a4d to c5a8128 Compare August 18, 2023 05:51
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.1 chore(deps): update dependency vitest to ^0.34.2 Aug 18, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c5a8128 to 1d6354d Compare August 26, 2023 08:54
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.2 chore(deps): update dependency vitest to ^0.34.3 Aug 26, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1d6354d to db20734 Compare September 8, 2023 11:56
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.3 chore(deps): update dependency vitest to ^0.34.4 Sep 8, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from db20734 to 315fcfb Compare September 22, 2023 05:24
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.4 chore(deps): update dependency vitest to ^0.34.5 Sep 22, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 315fcfb to 8fdf4bb Compare September 30, 2023 08:30
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.5 chore(deps): update dependency vitest to ^0.34.6 Sep 30, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8fdf4bb to 2bb9c59 Compare August 12, 2025 20:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2bb9c59 to 27a3f3e Compare August 23, 2025 15:36
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 27a3f3e to 62b9d2c Compare September 1, 2025 04:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 62b9d2c to e98da10 Compare September 26, 2025 00:16
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e98da10 to 5d352ee Compare October 23, 2025 19:32
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 373ea80 to bd0558c Compare November 19, 2025 22:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from bd0558c to d36a97f Compare January 1, 2026 19:44
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d36a97f to 9f07579 Compare January 9, 2026 15:49
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 5a6907e to 3d29d18 Compare January 24, 2026 11:32
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3d29d18 to 8995f34 Compare February 3, 2026 07:34
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8995f34 to 3f96c10 Compare February 13, 2026 15:44
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3f96c10 to 1adaef1 Compare March 8, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants