chore: upgrade vitest to v4 (blocked on vitepress 2.0 stable)

[rickcedwhat-ai]

Context

vitest 4.x requires vite >=6, but vitepress@1.x bundles vite@5.x as a hard dependency. Under pnpm's strict peer resolution this causes a fatal crash at test startup:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './module-runner' is not defined
by "exports" in .../vite/package.json

Dependabot PR #116 surfaces this — it was closed because the upgrade can't land until the vite peer conflict is resolved.

What needs to happen

1. vitepress 2.0 stable ships — it bundles vite@^7, which satisfies vitest 4's peer dep.

   • Current latest: 1.6.4 (stable), 2.0.0-alpha.17 (next)
   • Track releases: https://github.com/vuejs/vitepress/releases
   • Once vitepress@2.0.0 lands on the latest npm tag, Dependabot will automatically open a PR for it.

2. Merge the vitepress 2.0 Dependabot PR — verify docs build and custom Vue components still compile.

3. Remove the vitest ignore rules in .github/dependabot.yml — Dependabot will then re-open the vitest 4 bump and CI should pass.

Why Dependabot won't spam us in the meantime

.github/dependabot.yml has been updated to ignore vitest >= 4, @vitest/ui >= 4, and @vitest/coverage-v8 >= 4 until this is resolved.

References

• Closed PR: chore(deps-dev): bump the weekly-npm-dependencies group with 5 updates #116
• vitepress releases: https://github.com/vuejs/vitepress/releases
• vitest 4 changelog: https://github.com/vitest-dev/vitest/blob/main/CHANGELOG.md

Automated upstream check

type: npm
package: vitepress
condition: latest >= 2.0.0
blocked-pr: 116

upstream-check

type: npm
package: vitepress
condition: latest >= 2.0.0

[rickcedwhat]

@rickcedwhat-ai upstream watch npm vitepress >= 2.0.0

[rickcedwhat-ai]

🔍 Now watching vitepress — will notify when latest >= 2.0.0.

Added upstream-blocker:waiting label.

Checked every Monday at 09:00 UTC. Use @rickcedwhat-ai upstream check to run immediately.

[rickcedwhat]

@rickcedwhat-ai help

[rickcedwhat-ai]

@rickcedwhat-ai commands

On issues:

Command	Description
@rickcedwhat-ai upstream watch npm <pkg> >= <version>	Register upstream check + add :waiting label
@rickcedwhat-ai upstream check	Immediate semver check for this issue
@rickcedwhat-ai upstream schedule <delay>	Re-check after delay (e.g. 2w, 3d)
@rickcedwhat-ai upstream link pr #N	Link a blocked PR to this issue
@rickcedwhat-ai upstream unblock	Manually mark this issue as cleared

On PRs:

Command	Description
@rickcedwhat-ai coderabbit retry <delay>	Schedule a CodeRabbit review after delay (e.g. 36m)

Anywhere:

Command	Description
@rickcedwhat-ai reminder <delay>	Post a reminder comment here after delay (e.g. 2h, 1d)