monorepo-and-tooling

Configure Turborepo pipelines by defining dependsOn, inputs, and outputs in turbo.json to establish task graphs and enable predictable cross-package caching in pnpm workspaces. This structure ensures correct build ordering and stores cached outputs for faster subsequent runs.

The best way to share configs is centralizing them into dedicated packages/* directories, allowing apps to reference them as internal workspace dependencies. This avoids duplicated configuration files and ensures consistent linting and type checking across the monorepo.

Using workspace:* ensures reliable internal package resolution within pnpm workspaces, linking local packages correctly instead of fetching published versions. This prevents version mismatches and maintains accurate dependency graphs across monorepo apps and shared packages.

Common monorepo gotchas include using relative imports across packages, misaligned dependency versions, and circular dependencies. Avoid these by referencing internal packages via workspace:* and always running tasks through Turbo to maintain correct boundaries and build orders.

This setup applies to both JavaScript and TypeScript monorepos using pnpm workspaces and Turborepo. It supports Next.js apps, shared internal packages, and per-app deployment workflows while standardizing shared TypeScript, ESLint, and Tailwind configurations.