Build and runtime errors

Most build and runtime errors come down to a small handful of misconfigurations.

ERESOLVE / peer dependency conflict during npm install

Add a .npmrc file with:

legacy-peer-deps=true

Then re-run npm install. Vercel and most CI providers will pick up the file automatically.

"Can't reach database server"

Your DATABASE_URL is missing or wrong. For Neon and Supabase, the URL must include ?sslmode=require at the end. Confirm the URL works locally with npx prisma db pull.

Prisma "Unknown arg" or missing column

You changed the schema but didn't regenerate the client. Run:

npx prisma db push

npx prisma generate

Then restart your dev server — the Prisma client is bundled into the running process and won't reload on its own.

"Element type is invalid… got: undefined"

You imported a component that doesn't exist or wasn't exported. Double-check the import path and whether the component uses a named or default export.

Hydration mismatch

Some piece of state was different between server and client. Common causes:

• Reading window, localStorage, or navigator outside a useEffect.

• Time-based defaults (new Date()) used in JSX that the server and client computed differently.

• Random ordering — wrap with useMemo and a stable seed.

Still stuck?

Open a support ticket from your portal with the full error, the command that triggered it, your OS / Node version, and the product order number.