Skip to content

chore: migrate to Vitest 5 and align Vite 8 catalog - #2872

Open
maxffarrell wants to merge 3 commits into
huntabyte:mainfrom
maxffarrell:codex/vitest5-vite8
Open

maxffarrell wants to merge 3 commits into
huntabyte:mainfrom
maxffarrell:codex/vitest5-vite8

Conversation

@maxffarrell

Copy link
Copy Markdown
Contributor

Upgrade both test packages from Vitest 4.1.10 to 5.0.0 and regenerate the lockfile. Align the stale workspace catalog with Vite 8.1.5 and Svelte Vite plugin 7.2.0, which the docs already use, and require a Node version supported by Vitest 5 at the private monorepo root.

Reviewed the official Vitest 5 migration guide, the preceding Vitest 4 guide, and the Vite migration guide. Current upstream already uses Vitest 4 and Vite 8; no test or application source changes are required. Published CLI runtime requirements are unchanged.

Validation on Node 26.8.1 / pnpm 10.32.1:

  • CI=true pnpm test: 260 tests passed across 23 files, including generated registry fixtures and CLI snapshots.
  • pnpm lint: passed.
  • pnpm check: passed, zero Svelte errors or warnings.
  • CI=true pnpm build:docs: passed, including Cloudflare adapter output.
  • pnpm install --frozen-lockfile --ignore-scripts --offline: passed.

Copilot AI lite review requested due to automatic review settings September 5, 2026 02:46
@changeset-bot

changeset-bot Bot commented Sep 5, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 224f45e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are a consistent dependency/version alignment (Vitest/Vite/Node engines) with corresponding lockfile updates and no indicated source-level behavior changes required.

Pull request overview

This PR upgrades the monorepo’s testing setup to Vitest 5 and refreshes the pnpm workspace dependency catalog to match the Vite/Svelte tooling versions already used by the docs, along with a lockfile regeneration reflecting the new dependency graph.

Changes:

  • Bump Vitest from ^4.1.10 to ^5.0.0 in the two workspaces that run tests (CLI + registry).
  • Update the pnpm workspace catalog to Vite ^8.1.5 and @sveltejs/vite-plugin-svelte ^7.2.0.
  • Update the root engines.node constraint to match Vitest 5’s supported Node range and regenerate pnpm-lock.yaml.
File summaries
File Description
sv-addons/registry/package.json Updates the registry workspace test runner to Vitest 5.
packages/cli/package.json Updates the CLI workspace test runner to Vitest 5.
pnpm-workspace.yaml Aligns catalog versions for Vite and Svelte’s Vite plugin with current tooling.
package.json Raises the monorepo root Node engine range to match Vitest 5 requirements.
pnpm-lock.yaml Regenerated lockfile reflecting Vitest 5 and related transitive updates.
Review details

Files not reviewed (1)

  • pnpm-lock.yaml: Generated file
  • Files reviewed: 4/5 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor
built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
shadcn-svelte ✅ Ready (View Log) Visit Preview 224f45e

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