Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Jun 6, 2023

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

@changeset-bot

changeset-bot Bot commented Jun 6, 2023

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 81fce1a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@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 6, 2023
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 86929eb to 2c60957 Compare July 6, 2023 15:36
@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 from 2c60957 to fdf0520 Compare August 1, 2023 15:58
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from fdf0520 to ff3389f Compare April 11, 2024 14:38
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from ff3389f to b7599af Compare June 7, 2024 22:00
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from e2d2299 to 5169d44 Compare August 13, 2025 17:51
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 5169d44 to f59ae92 Compare August 31, 2025 12:23
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from f59ae92 to 843b5ff Compare September 25, 2025 16:48
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 843b5ff to 1720d61 Compare November 10, 2025 17:44
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 1720d61 to bfedec0 Compare January 8, 2026 18:56
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from bfedec0 to e0f45f8 Compare January 19, 2026 20:13
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from e0f45f8 to 99b9dbc Compare February 12, 2026 13:30
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 99b9dbc to 7ce93de Compare March 5, 2026 18:58
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 7ce93de to f66cf8b Compare April 1, 2026 17:34
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from f66cf8b to f9d8bf2 Compare May 12, 2026 10:43
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^0.34.0 chore(deps): update vitest monorepo to ^0.34.0 Jun 2, 2026
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from f9d8bf2 to b0e1da5 Compare June 13, 2026 19:54
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to ^0.34.0 chore(deps): update vitest monorepo Jun 22, 2026
@renovate renovate Bot changed the title chore(deps): update vitest monorepo chore(deps): update dependency vitest to ^0.34.0 Jun 25, 2026
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from b0e1da5 to 969e1ee Compare July 17, 2026 02:08
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 969e1ee to d02e95c Compare July 30, 2026 17:16
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from d02e95c to 14af957 Compare August 26, 2026 12:53
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 14af957 to 81fce1a Compare September 2, 2026 22:30
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