Skip to content

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

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 29, 2023

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 a83decc to a220b19 Compare April 9, 2023 15:34
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v0.29.8 chore(deps): update dependency vitest to ^0.30.0 Apr 9, 2023
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^0.30.0 chore(deps): update dependency vitest to ^0.31.0 May 3, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from a220b19 to 60be151 Compare May 3, 2023 21:47
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 60be151 to 8539775 Compare May 17, 2023 05:51
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 8539775 to 88e02ff Compare June 10, 2023 02:52
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^0.31.0 chore(deps): update dependency vitest to ^0.32.0 Jun 10, 2023
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^0.32.0 chore(deps): update dependency vitest to ^0.33.0 Jul 8, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 88e02ff to 5500a86 Compare July 8, 2023 02:43
@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 2, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 5500a86 to 366800b Compare August 2, 2023 05:59
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 366800b to 28e3b63 Compare August 13, 2025 23:27
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 28e3b63 to 44d6ab5 Compare August 22, 2025 04:06
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 44d6ab5 to f95eb0b Compare September 1, 2025 01:09
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from f95eb0b to d94accf Compare September 26, 2025 03:46
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from d94accf to f88e544 Compare October 23, 2025 07:57
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 9082d46 to 9f40263 Compare November 19, 2025 19:36
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 9f40263 to ce8c303 Compare December 31, 2025 23:50
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from ce8c303 to f10f4f1 Compare January 9, 2026 15:41
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from a4edfc3 to fcb02ef Compare January 24, 2026 10:58
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from fcb02ef to 4c02c88 Compare February 3, 2026 04:07
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 4c02c88 to a9f6136 Compare March 8, 2026 10:19
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from a9f6136 to 0f62c3b Compare April 15, 2026 15:42
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 0f62c3b to c53d01e Compare April 30, 2026 03:59
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from c53d01e to 32e4e91 Compare May 13, 2026 20:17
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