Skip to content

Conversation

@dmmulroy
Copy link

@dmmulroy dmmulroy commented Dec 15, 2025

Problem

  1. no unified test runner - each package runs tests independently, no single command
  2. version drift - packages have different vitest versions, subtle incompatibilities
  3. deprecated workspace config - using vitest.workspace (deprecated in 3.2)
  4. no shared config - timeout/globals duplicated across packages
  5. pool-workers version lock - @cloudflare/vitest-pool-workers only supports 2.0.x-3.2.x

Solution

root vitest.config.ts orchestrates all package tests via projects config. shared settings in vitest.shared.ts. syncpack keeps versions aligned. pinned to vitest 3.2.4 until pool-workers supports 4.x.

Changes

  • add root vitest.config.ts with projects config
  • add vitest.shared.ts for common test settings
  • update packages/core and packages/storage to use shared
  • exclude vitest configs and test dirs from packages/tsconfig.json (build was failing)
  • downgrade vitest to 3.2.4 (pool-workers incompatible w/ 4.x)
  • add syncpack for version sync

Verification

  • pnpm test:run - 17 tests pass (core + storage)
  • pnpm test:ui - UI launches at localhost:51204

@dmmulroy dmmulroy marked this pull request as draft December 15, 2025 20:12
@dmmulroy dmmulroy changed the title unify vitest config w/ projects pattern unify vitest config with projects pattern Dec 15, 2025
@dmmulroy dmmulroy changed the title unify vitest config with projects pattern feat: unify vitest config with projects pattern Dec 15, 2025
@dmmulroy dmmulroy force-pushed the feat/vitest-config branch 2 times, most recently from e41f98e to 90fe8bb Compare December 17, 2025 18:40
- add root vitest.config.ts with projects config
- add vitest.shared.ts for common test settings
- update packages/core and packages/storage to use shared
- downgrade vitest to 3.2.4 (pool-workers incompatible w/ 4.x)
- add syncpack for version sync
@dmmulroy dmmulroy marked this pull request as ready for review December 18, 2025 17:27
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