Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade vitest from 0.33.0 to 0.34.1 #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

leonardoadame
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade vitest from 0.33.0 to 0.34.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-08-01.
Release notes
Package name: vitest
  • 0.34.1 - 2023-08-01

       🐞 Bug Fixes

        View changes on GitHub
  • 0.34.0 - 2023-08-01

       🚨 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.
    • 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
  • 0.33.0 - 2023-07-06
    Read more
from vitest GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

2 participants