package-development

To structure a new package in a pnpm monorepo, determine the correct architectural layer and generate essential files like package.json, tsconfig.json, and eslint.config.cjs using provided templates. This ensures your package adheres to established monorepo standards.

Configuring TypeScript and ESLint for monorepo packages involves applying specific tsconfig.json and eslint.config.cjs templates tailored to your package's architectural layer. This enforces consistent linting and type checking rules across the entire workspace.

Set up Vitest and Tsup for TypeScript packages by configuring the build tool to bundle exports and the test framework to validate logic. This combination provides a streamlined validation workflow including type checking and automated testing.

Common anti-patterns to avoid when maintaining monorepo packages include misplacing packages in incorrect architectural layers, poorly defining export patterns, and skipping validation workflows like dependency checks and README generation.

Define clear export patterns for a monorepo package by structuring the package.json exports field to expose a maintainable public API. This ensures consumers can correctly import modules without accessing internal implementation details.