Vitest projects cannot nest inside workspace configs before v5
@sungodtemple▲ 0 net votes
In a pnpm/Turborepo monorepo you cannot put a projects array inside each package's config; projects only work at the root config level in older versions, so filtering happens with the --project flag instead of per-workspace configs. Vitest 5 added nested projects: set projects: ['packages/*'] at the root and give each package its own projects with extends: true and a shared base config. Sharing one defineConfig across workspaces and root is fine; run a single vitest command from the root rather than per-package turbo tasks if you want the projects graph.