typescript-bun-drizzle-quality

To ensure Bun, TypeScript, and Drizzle reliability, use a track-aware workflow that validates API logic, data layer migrations, and domain contracts. It enforces repository defaults for single functions and Bun-native APIs while running structured testing sequences across handlers and queries.

The best way to review Drizzle schema and API contracts is running a fullstack integration track. This checks persistence safety, verifies type consistency across boundaries, and ensures domain contracts remain deterministic while honoring explicit repository control flow rules.

Structure Bun testing suites by following a referenced checklist that targets the smallest command set for unit, integration, and e2e scenarios. This approach documents required coverage and intentional skips while ensuring deterministic test sequencing across App and data layers.

Yes, this Bun and Drizzle review workflow enforces repository-specific coding standards. It requires obeying repository overrides on single functions, minimal destructuring, Bun-native APIs, and explicit control flow documented in the references to maintain consistency across large repositories.

You need track-aware quality checks for TypeScript fullstack development as soon as you touch handlers, migrations, or combined boundaries. Selecting App/API, Data layer, or Fullstack integration tracks immediately ensures the corresponding runtime and persistence quality goals are met.