build-validation

Build validation automates a complete suite of checks including TypeScript type checking, ESLint linting, token generation, contrast validation, and production builds. Run it after code changes to catch errors, accessibility violations, and regressions before they reach CI/CD pipelines, with detailed error analysis and fix recommendations.

Yes. Build validation tracks build times and performance metrics alongside error detection, identifying bottlenecks and new performance issues introduced by recent changes. It gates CI pipelines and provides regression detection to ensure reliable releases.

Build validation executes token generation, contrast validation for accessibility, TypeScript type checking, ESLint linting, and production builds. It categorizes errors by type, provides root cause analysis with file and line references, and recommends specific fixes.

Yes. Build validation requires pnpm as a dependency to execute its validation workflow and manage the build pipeline across token generation, type checking, linting, and production builds.

Build validation automates the entire validation pipeline, eliminating manual steps prone to human error. It provides rapid feedback, consistent checks across all validation types, and detailed error analysis to ensure every release meets quality standards.