build-pipeline

A build pipeline orchestrates multiple checks sequentially—dead code detection, formatting, linting, type checking, testing, and production build—in fail-fast order so the process stops at the first failure. Use bun run knip && bun run format && bun run lint && bun run typecheck && bun test && bun run build to execute all stages and produce a production bundle only after every check passes.

Fail-fast execution stops the pipeline immediately when any stage fails, preventing wasted time on later checks. This approach ensures you catch code quality issues—formatting problems, type errors, or test failures—before attempting a production build, saving resources and accelerating feedback.

Individual checks can run separately using bun run knip, bun run format, bun run lint, bun run typecheck, bun test, or bun run build as standalone commands. The complete pipeline chains them together with fail-fast termination; choose individual commands for targeted validation during development and the full pipeline before production deployment.

Dead code detection identifies unused imports, variables, functions, and types that clutter your codebase and slow compilation. Running knip as the first pipeline stage surfaces these issues early so you can remove unnecessary code before formatting, linting, and testing stages proceed.

Type checking catches structural and type errors at compile time before runtime execution, eliminating entire categories of bugs that tests would otherwise surface. Running typecheck before test in the pipeline reduces test scope to logic validation and ensures type safety across your production build.

Yes, the build pipeline is designed for TypeScript projects using bun as the runtime. It orchestrates typescript-aware checks—type checking, linting with TypeScript support, and testing—alongside formatting and dead code detection to validate and bundle TypeScript code for production.