Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.6.10 -> 8.6.12
vitest	^0.33.0 -> ^0.34.0

---

Release Notes

pnpm/pnpm (pnpm)

v8.6.12

Compare Source

Patch Changes

• Make the error message friendlier when a user attempts to run a command that does not exist #​6887.
• pnpm patch should work correctly when shared-workspace-file is set to false #​6885.
• pnpm env use should retry deleting the previous Node.js executable #​6587.
• pnpm dlx should not print an error stack when the underlying script execution fails #​6698.
• When showing the download progress of large tarball files, always display the same number of digits after the decimal point #​6901.
• Report download progress less frequently to improve performance #​6906.
• pnpm install --frozen-lockfile --lockfile-only should fail if the lockfile is not up to date with the package.json files #​6913.

Our Gold Sponsors

Our Silver Sponsors

v8.6.11

Compare Source

Patch Changes

• Change the install error message when a lockfile is wanted but absent to indicate the wanted lockfile is absent, not present. This now reflects the actual error #​6851.
• When dealing with a local dependency that is a path to a symlink, a new symlink should be created to the original symlink, not to the actual directory location.
• The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
• Don't print "added" stats, when installing with --lockfile-only.
• Installation of a git-hosted dependency should not fail if the pnpm-lock.yaml file of the installed dependency is not up-to-date #​6865.
• Don't ignore empty strings in params #​6594.
• Always set dedupe-peer-dependents to false, when running installation during deploy #​6858.
• When several containers use the same store simultaneously, there's a chance that multiple containers may create a temporary file at the same time. In such scenarios, pnpm could fail to rename the temporary file in one of the containers. This issue has been addressed: pnpm will no longer fail if the temporary file is absent but the destination file exists.
• Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors

vitest-dev/vitest (vitest)

v0.34.1

Compare Source

   🐞 Bug Fixes

• Pass --experimental-vm-worker-memory-limit to tinypool  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)

    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes

• Transform mode affects only test files, not regular files  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)
• Remove @vitest/coverage-c8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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

• Support describe.sequential  -  by @​fenghan34 and @​dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)
• Support config junit reporter className with env  -  by @​InfiniteXyy in https://github.com/vitest-dev/vitest/issues/3808 (e8bc4)
• Running vitest with --related --watch reruns non-affected tests if they were changed during a run  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)

   🐞 Bug Fixes

• Isolate workers between envs and workspaces  -  by @​AriPerkkio (ed4e0)
• Modify condition  -  by @​btea (a78e6)
• Module Graph view is blocking the Console view  -  by @​g4rry420 (3b5f9)
• Port the latest defineConfig type from vite  -  by @​sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)
• Don't overwrite Node.js URL global  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3828 (cdab4)
• ForceRerunTriggers correctly triggers a rerun  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3829 (17988)
• browser:
  • Don't inline magic-string and estree-walker  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3726 (ee937)
  • Multi-suite coverage  -  by @​elby22 in https://github.com/vitest-dev/vitest/issues/3806 (5de9a)
• core:
  • DataView comparison does not work in toStrictEqual  -  by @​Dunqing (52aef)
• coverage:
  • V8 provider to pick source maps without url query params  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3784 (280e6)
  • Update istanbul-lib-instrument to v6 to fix vulnerable dependency  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)
  • Exclude vite virtual modules by default  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3794 (3c851)
• node:
  • Guard error info  -  by @​btea (88b39)
• vite-node:
  • Always treat node_modules as modulesDirectory  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3830 (51ab8)
  • Normalize drive letter to keep the same reference to a module  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3836 (45521)
  • Correctly resolve hmr filepath  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3834 (711a6)
• watch:
  • Clear screen on all terminals  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3661 (8bd26)

   🏎 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: Branch creation - "on the first day of the month" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.