Migrate workspace library tooling to Vite+

[Copilot]

This updates the workspace to use Vite+ for the shared library packages and root task orchestration, replacing the previous split setup around Turbo, tsup, Prettier, and Vitest where those tools were directly used by the libraries. It also rewrites the remaining Vitest imports and aligns package metadata/config with Vite+ outputs.

• Root tooling migration

  • Replaced Turbo-based root scripts with Vite+ task entrypoints:
    • build → vp run -r build
    • dev → vp run -r dev
    • lint → vp run -r lint
    • check / test added at the root
  • Added a root vite.config.ts for shared Vite+ config:
    • moved formatting settings from .prettierrc into fmt
    • added root test discovery for package tests
    • enabled Vite+ task caching for workspace scripts
  • Removed obsolete root config/dependency:
    • deleted turbo.json
    • deleted .prettierrc
    • replaced turbo with vite-plus

• Library packaging migration

  • Migrated the publishable packages from tsup to vp pack:
    • packages/html
    • packages/markdown
    • packages/contentsgarten
    • packages/client-utils
    • packages/server-utils
  • Added package-local vite.config.ts files with pack configuration for each migrated library
  • Updated package entry metadata to match Vite+ pack output (dist/index.mjs, dist/index.d.mts)

• Test migration

  • Rewrote the remaining Vitest imports from vitest to vite-plus/test
  • Added package test scripts where tests already existed so those packages run through Vite+

• Dependency cleanup

  • Removed direct tsup and vitest usage from the migrated packages after the import/script rewrites were in place
  • Switched the repo to depend on vite-plus as the shared toolchain surface

Example of the test import rewrite:

// before
import { test, expect, suite } from 'vitest'

// after
import { test, expect, suite } from 'vite-plus/test'

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/contentsgarten/contentsgarten/wiki.wonderful.software/node_modules/.bin/../next/dist/bin/next build bash --no�� che/node-gyp/24.14.0/include/node (dns block)
• www.npmjs.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Migrate to Vite+</issue_title>
<issue_description>Migrate this project to Vite+. Vite+ replaces the current split tooling around runtime management, package management, dev/build/test commands, linting, formatting, and packaging. Run vp help to understand Vite+ capabilities and vp help migrate before making changes. Use vp migrate --no-interactive in the workspace root. Make sure the project is using Vite 8+ and Vitest 4.1+ before migrating.

After the migration:

• Confirm vite imports were rewritten to vite-plus where needed
• Confirm vitest imports were rewritten to vite-plus/test where needed
• Remove old vite and vitest dependencies only after those rewrites are confirmed
• Move remaining tool-specific config into the appropriate blocks in vite.config.ts

Command mapping to keep in mind:

• vp run <script> is the equivalent of pnpm run <script>
• vp test runs the built-in test command, while vp run test runs the test script from package.json
• vp install, vp add, and vp remove delegate through the package manager declared by packageManager
• vp dev, vp build, vp preview, vp lint, vp fmt, vp check, and vp pack replace the corresponding standalone tools
• Prefer vp check for validation loops

Finally, verify the migration by running: vp install, vp check, vp test, and vp build

Summarize the migration at the end and report any manual follow-up still required.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Migrate to Vite+ #462

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview