Tests in parallel + master `pnpm install -r` is THE install command

Tests parallel, pnpm install -r from master

Tests in parallel + master `pnpm install -r` is THE install command

The rule

Every app and every package gets:

• Vitest unit tests
• Playwright E2E tests
• Storybook for UI islands where applicable

Master CI matrix-fans all suites in parallel.

The user always works from c:/D/oriz/ (the umbrella repo). Per-submodule pnpm install is forbidden — only pnpm install -r from master.

Install commands

Fresh clone:

git clone --recurse-submodules https://github.com/chirag127/workspace c:/D/oriz
cd c:/D/oriz
pnpm install -r

Update existing:

cd c:/D/oriz
git submodule update --init --recursive --remote
pnpm install -r

Why

Single source of truth for dependency graph + cross-package linking (workspace:* protocol). Per-submodule install creates parallel node_modules trees that drift. Always-master install keeps everything coherent.

How to apply

• New submodule: scaffold its package.json, add it to pnpm-workspace.yaml glob, then pnpm install -r from master.
• New test: add Vitest config to the relevant submodule’s vitest.config.ts. The master CI matrix auto-picks it up.

Cross-refs

• Parallel-fan-out-by-default sibling → [[rules/interaction/parallel-fan-out-by-default]]
• Linux-only CI runners → [[rules/linux-ci-only]]
• Install runbook → [[runbooks/install-and-bootstrap]]

Edit on GitHub · Back to index