What problem does it solve?
Patterns and gotchas for extracting and maintaining workspace packages in this pnpm/tsup monorepo — package boundary design, dts emission, Tailwind v4 cross-package CSS, and the strict-mode / library-typing interactions that surface when primitives ship from a published package.
Core Features & Use Cases
- Co-locate generator CLIs with the artifacts they produce, placing scripts in packages/<x>/scripts and ensuring the consumer's workflows map to the corresponding tsup/exports entries.
- Align exports with tsup entry points, and document how to include scripts in the published package via the files field to ensure CLI and generator accessibility.
- Detect and prevent misclassified primitives by following the project rule that design concerns used by 2+ consumers live in shared packages, and move app-specific concerns to apps/web when extracting.
- Preserve client directive semantics (use client) across bundles to avoid server/client component resolution issues in Next.js-like environments.
Quick Start
Audit your monorepo against these guidelines and adjust package boundaries accordingly.