Turborepo

Turborepo coordinates workspace-owned repository tasks across applications and packages.

The task ownership model is defined in ADR-011.

Root commands

The primary root commands that delegate to Turbo are:

pnpm dev
pnpm build
pnpm test
pnpm lint
pnpm lint:fix
pnpm check-types

Formatting remains a repository-owned operation rather than a duplicated workspace Turbo task.

The public repository build command executes:

turbo run build build-storybook

Normal workspace build tasks depend on builds from upstream workspace dependencies:

"dependsOn": ["^build"]

The current production outputs include:

.next/**
build/**
storybook-static/**

The Storybook artifact uses the specialized internal task:

@repo/ui#build-storybook

This keeps Storybook out of the normal workspace dependency-build semantics while still including it in the root pnpm build contract.

Next.js cache and development outputs are excluded from cached production outputs where appropriate.

The root test command executes:

turbo run test

Every workspace that exposes a real test task participates automatically.

The UI workspace currently provides the repository browser test suite.

The test task currently bypasses Turbo caching so browser validation executes on each quality-gate invocation.

Development tasks are:

This allows application and Storybook development servers to remain active.

The root type-check command executes:

turbo run check-types

Each participating workspace defines its own implementation.

Repository workspaces expose a common lint task which Turbo runs across the workspace graph.

Shared ESLint policy and workspace lint execution are intentionally separate concerns.

Formatting does not currently use turbo run format.

Prettier owns regular files across the entire repository, including root and automation files, while Remark owns Docusaurus MDX.

A workspace-level formatting graph should only be introduced if future workspace technologies genuinely require different formatting implementations.