Skip to content

Update dependency vitest to v0.34.6#170

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

Update dependency vitest to v0.34.6#170
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Aug 2, 2023

This PR contains the following updates:

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

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 is behind base branch, 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
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Aug 2, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.6.5
npm error Found: vitest@0.34.6
npm error node_modules/vitest
npm error   dev vitest@"0.34.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Conflicting peer dependency: vitest@0.33.0
npm error node_modules/vitest
npm error   peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-07T00_49_41_986Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-07T00_49_41_986Z-debug-0.log

@renovate renovate Bot added the renovate Created by Renovate label Aug 2, 2023
@netlify
Copy link
Copy Markdown

netlify Bot commented Aug 2, 2023

Deploy Preview for anohi-no-tweet ready!

Name Link
🔨 Latest commit c817084
🔍 Latest deploy log https://app.netlify.com/projects/anohi-no-tweet/deploys/688b581ed5b3b800081b7ff9
😎 Deploy Preview https://deploy-preview-170--anohi-no-tweet.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@renovate renovate Bot changed the title Update dependency vitest to v0.34.1 Update dependency vitest to v0.34.2 Aug 17, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from e0003cb to abdeff3 Compare August 17, 2023 11:44
@renovate renovate Bot changed the title Update dependency vitest to v0.34.2 Update dependency vitest to v0.34.3 Aug 25, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from cfd37c6 to e49a32e Compare August 28, 2023 13:41
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 98686d6 to 44f9317 Compare September 6, 2023 14:56
@renovate renovate Bot changed the title Update dependency vitest to v0.34.3 Update dependency vitest to v0.34.4 Sep 8, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from 3dc3872 to 8d73586 Compare September 14, 2023 04:49
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from e9523ba to 1c01b4f Compare September 18, 2023 00:53
@renovate renovate Bot changed the title Update dependency vitest to v0.34.4 Update dependency vitest to v0.34.5 Sep 21, 2023
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 8c26fe1 to a9be119 Compare September 24, 2023 12:19
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 77bf9f5 to 62a1e2d Compare November 27, 2023 01:39
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from ef658a5 to f44455c Compare December 13, 2023 03:42
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 69ef2c9 to 573ec0c Compare December 14, 2023 04:18
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 573ec0c to 40081a4 Compare December 25, 2023 14:38
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from a483cc7 to a62f2c0 Compare January 11, 2024 12:23
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 11 times, most recently from b21eada to f5b5e1c Compare April 14, 2024 12:49
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from f5b5e1c to b92eedd Compare April 23, 2024 03:09
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 12, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.6.5
npm error Found: vitest@0.34.6
npm error node_modules/vitest
npm error   dev vitest@"0.34.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Conflicting peer dependency: vitest@0.33.0
npm error node_modules/vitest
npm error   peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T14_08_51_193Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T14_08_51_193Z-debug-0.log

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Dec 8, 2024

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

renovate Created by Renovate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants