Ensure Vercel applies Prisma migrations before build

Author: DevCalebR

README.md

@@ -400,9 +400,11 @@ Creating a dedicated simulator workspace:
    - `NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in`
    - `NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up`
    - In Clerk Dashboard, allow both URLs on the deployed origin.
-6. Run Prisma migrations against your production database:
-   - Either via CI/CD step: `npx prisma migrate deploy`
-   - Or manually once after deploy
+6. Vercel deploys should use the repo build command `npm run vercel-build`:
+   - This runs `npm run db:generate`
+   - Then `npm run db:deploy`
+   - Then `npm run build`
+   - If the Vercel dashboard overrides the build command, set it to `npm run vercel-build`
 7. Configure Stripe webhook to the Vercel domain.
 8. Configure Twilio phone number webhooks (or buy the number through the app after deploy).
    - Helper: `npm run webhooks:print` (redacts the shared token by default)
@@ -439,8 +441,9 @@ Use this checklist before sending paid traffic to `callbackcloser.com` or allowi
    - `npm run typecheck`
    - `npm run build`
 3. Confirm Vercel production env vars match `docs/PRODUCTION_ENV.md`.
-4. Apply production Prisma migrations:
-   - `npx prisma migrate deploy`
+4. Confirm the deploy path applies Prisma migrations before runtime:
+   - repo build command: `npm run vercel-build`
+   - exact migration step inside it: `npm run db:deploy`
    - optional smoke: `npm run db:smoke`
 5. Confirm Stripe production setup:
    - live products/prices exist

docs/DB_NEON_PRISMA.md

@@ -69,6 +69,22 @@ Recommended:
 - Preview uses preview/staging Neon DB URLs (pooled + direct)
 - Production uses production Neon DB URLs (pooled + direct)
 
+### Vercel build command
+
+This repo expects Vercel to use:
+
+```txt
+npm run vercel-build
+```
+
+That script runs, in order:
+
+1. `npm run db:generate`
+2. `npm run db:deploy`
+3. `npm run build`
+
+This keeps Prisma Client generation explicit and applies additive Prisma migrations through `DIRECT_DATABASE_URL` before `next build` completes.
+
 ## Common Mistake to Avoid
 
 Using the pooled `-pooler` URL for Prisma migrations can cause migration problems or connection behavior issues. Keep migrations on `DIRECT_DATABASE_URL` (direct endpoint) and runtime on `DATABASE_URL` (pooled endpoint).

package.json

@@ -5,6 +5,7 @@
   "scripts": {
     "dev": "next dev",
     "build": "next build",
+    "vercel-build": "npm run db:generate && npm run db:deploy && npm run build",
     "start": "next start",
     "test": "tsx --test tests/*.test.ts",
     "test:twilio": "tsx --test tests/twilio-*.test.ts",

vercel.json

@@ -1,4 +1,4 @@
 {
   "framework": "nextjs",
-  "buildCommand": "npm run build"
+  "buildCommand": "npm run vercel-build"
 }