Pitfall Preferences jobs-apply

Vercel Monorepo Build Chain

pitfalldeploymentvercelcareer

What Happened

4 deployment-related commits in 20 minutes (ba69e09, 6065c0d, 222569e at 22:01-22:11) reveal a painful Vercel deployment struggle. The dashboard depends on @jobs-apply/types, @jobs-apply/database, and @jobs-apply/ai packages that must be built BEFORE the dashboard build.

Root Cause

Three compounding issues: (1) Vercel’s build command ran only the dashboard build, not the dependency packages. (2) Git-triggered deploys were sensitive to author identity : the git author didn’t match Vercel’s expected author, requiring a separate “trigger deploy” commit. (3) The CLAUDE.md had incorrect build/deploy instructions that were cargo-culted from the previous single-package architecture.

Fix

Configured Vercel build command to build dependency packages first: cd packages/types && npm run build && cd ../database && npm run build && cd ../dashboard && npm run build. Updated CLAUDE.md with correct monorepo build sequence.

Lesson

Monorepo builds on Vercel need explicit dependency chain configuration. The platform doesn’t infer inter-package build order from package.json workspaces. Test the build command locally with vercel build before pushing, and never assume a CI/CD platform will replicate your local monorepo build graph.