validate-component

To validate a new Vue component, run pnpm lint, type-check, type-coverage, dts build, and Storybook build checks in a fixed order. This ensures the component meets TypeScript thresholds and documentation builds without breaking before committing it to the codebase.

The correct CI validation order for Vue components is lint, type-check, type-coverage, dts build, and finally Storybook build. This fixed sequence ensures deterministic checks and stops immediately upon the first failure to surface errors quickly.

No, component validation never runs pnpm install and never mutates the working tree. It acts as a non-mutating safety guardrail, strictly running checks and reporting pass or fail outcomes without altering your project files.

To stop Storybook builds from breaking, run a Storybook build check after scaffolding new Vue components. This validation step catches story errors early by building the documentation and reporting the first failing step with its output tail.

Type coverage checks fail during component scaffolding when the new Vue component does not meet the project's TypeScript thresholds. The validation process stops at the type-coverage step, surfaces the failure immediately, and provides the last output lines to speed up debugging.

Limitations of automated component validation include a strict 5-minute command timeout and first-failure stopping behavior without attempting auto-fixes. It also requires existing pnpm scripts and cannot resolve missing-script errors, which result in an unclear state.