chore(deps): bump vitest and vite-plus

[dependabot]

Bumps vitest to 4.1.11 and updates ancestor dependency vite-plus. These dependencies need to be updated together.

Updates vitest from 4.1.10 to 4.1.11

Release notes

Sourced from vitest's releases.

v4.1.11

   🐞 Bug Fixes

• Revive global concurrency limit for test lifecycle [backport to v4]  -  by @​sheremet-va and @​hi-ogawa in vitest-dev/vitest#10992 (5146d)
• browser:
  • Encode iframeId in tester iframe URL [backport to v4]  -  by @​sheremet-va, Pduhard and Claude Opus 4.8 in vitest-dev/vitest#10955 (10b2c)
  • Trigger playwright/chromium gc on lower disk availability [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode in vitest-dev/vitest#10951 (9851d)
• mocker:
  • Restrict redirect mocks to the fs allowlist [backport to v4]  -  by @​sheremet-va in vitest-dev/vitest#10974 (fe5a1)

    View changes on GitHub

Commits

• 9bd8d46 chore: release v4.1.11 (#10995)
• 9851dbc fix(browser): trigger playwright/chromium gc on lower disk availability [back...
• See full diff in compare view

Updates vite-plus from 0.2.9 to 0.3.1

Release notes

Sourced from vite-plus's releases.

vite-plus v0.3.1: manage package-manager versions with vp env

vp env now manages Node.js and package-manager versions together. This release also fixes TanStack Start routing and stale Vitest aliases.

Breaking Changes

Package-manager setup

Vite+ replaces Corepack with managed npm, pnpm, yarn, and bun commands. It removes the corepack shim and legacy global package-manager installations (#2391), by @​liangmiQwQ.

Replace Corepack setup commands in shell profiles, CI jobs, and Dockerfiles:

Previous setup	Replacement
corepack enable	vp env setup
vp install -g pnpm@<version>	vp env default pnpm@<version>
vp install -g yarn@<version>	vp env default yarn@<version>
vp install -g bun@<version>	vp env default bun@<version>
vp install -g corepack	Use the managed package-manager commands directly

Use vp env pin <manager>@<version> to set a project version.

vp env command scope and JSON output

Unscoped vp env commands now operate on Node.js and package managers. Package managers support independent defaults, project pins, session overrides, and installation commands (#2398), by @​liangmiQwQ.

Add node to limit an operation to Node.js, for example, vp env off node or vp env unpin node. Bare versions, such as vp env default 22.19.0, still select Node.js.

Update scripts that read JSON output:

Command	New output structure
vp env current --json	node and package_manager objects
vp env list --json, vp env list-remote --json	node and package_managers groups

See the environment guide.

vp pack migration to tsdown@0.23

vp pack now uses tsdown@0.23, which removes deprecated options and changes defaults (#2614), by @​fengmk2.

1. Run vp migrate to update supported static configurations and package scripts, including projects that already use Vite+.
2. Check migration warnings in vite.config.*, tsdown.config.*, and package.json.
3. Update dynamic configurations manually. Arrays built with .map() require manual changes, even when migration reports no warning.
4. Run vp pack to check the result.

Previous option	Replacement
bundle: false	unbundle: true
outExtension	outExtensions
publicDir / --public-dir	copy / --copy

... (truncated)

Commits

• 13e1e5a release: v0.3.1: manage package-manager versions with vp env (#2623)
• 0931d9b fix(cli): share Vite runtime through the core alias (#2617)
• 3bbae42 feat(migrate): upgrade pack config for tsdown 0.23 (#2614)
• 7123545 chore(deps): update dependency voidzero-dev/setup-vp to v1.19.0 (#2619)
• b87593c fix(cli): recover from stale Vitest aliases (#2605)
• 21f6c42 ci: gate npm publishes on dependency propagation (#2601)
• 809d8b8 feat(deps): upgrade upstream dependencies (#2613)
• 585353f docs: fix Zed Oxc configuration (#2592)
• 4f97f30 feat(cli): expose dependency alignment plans (#2600)
• 03b659c feat(cli): add --quiet to vp check (#2593)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.