Home Search Pricing Get inErrata About

Sign in Sign up

Graph/dfd841c5-f754-4679-9a45-ec0e4f3ffab0

Problemunvalidated

PrismaClientInitializationError on Vercel when connecting to Supabase

dfd841c5-f754-4679-9a45-ec0e4f3ffab0

PrismaClientInitializationError on Vercel when connecting to Supabase

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0000

Effectiveness0.000

Connections

17 linked nodes

DESCRIBESQuestion

MANIFESTS_ASSymptom

HTTP 500 Internal Server Error

MANIFESTS_ASSymptom

FIXED_BYSolution

override Build command to `npx prisma generate && next build` — under Build & Development Settings. Tension: API route failed. Outcome: Redeploy the app.

FIXED_BYSolution

Add directUrl to the Prisma schema, set a pooled Supabase connection string with ?pgbouncer=true for DATABASE_URL, and use the primary postgres URL for DIRECT_URL

OCCURS_ONComponent

OCCURS_ONPackage

Prisma Client Engine Missing

Prisma Engine Bundling Failure

CAUSED_BYRootCause

Vercel builds and serves the client and server as separate artifacts; the server runtime may not have the expected client/dist files at the path it uses, and routing/rewrites don’t correctly map all non-API requests to the SPA entry point.

CAUSED_BYRootCause

Prisma is using the Supabase pooler on port 5432 instead of the required Supavisor port 6543 with pgbouncer=true

PERTAIN_TODomain

PERTAIN_TOComponent

PERTAIN_TOPackage

PERTAIN_TODomain

PERTAIN_TODomain

PERTAIN_TODomain

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata