Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 1, 2023

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@vitest/ui (source) ^0.33.0 -> ^0.34.0 age confidence
vitest (source) ^0.33.0 -> ^0.34.0 age confidence

Release Notes

vitest-dev/vitest (@​vitest/ui)

v0.34.7

Compare Source

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
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

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Aug 1, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-guardian ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 10, 2025 0:30am
react-guardian-nbsx ❌ Failed (Inspect) Aug 10, 2025 0:30am

@github-actions
Copy link
Contributor

github-actions bot commented Aug 1, 2023

size-limit report 📦

Path Size
dist/index.mjs 559 B (0%)

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2193319 to 4d146a8 Compare December 12, 2023 18:15
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4d146a8 to fee6307 Compare December 22, 2023 17:12
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fee6307 to 7c1f68e Compare December 23, 2023 18:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7c1f68e to 57aac0c Compare December 31, 2023 18:42
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 57aac0c to e1101a0 Compare January 16, 2024 17:16
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e1101a0 to 95cf252 Compare January 17, 2024 17:22
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 95cf252 to 224702a Compare January 21, 2024 18:36
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 224702a to f57b3d9 Compare January 24, 2024 18:20
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f57b3d9 to 5041702 Compare January 27, 2024 17:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5041702 to e27d792 Compare February 1, 2024 18:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e27d792 to e857f12 Compare February 6, 2024 18:46
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e857f12 to b087c1b Compare February 7, 2024 18:37
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