npx prisma migrate dev freezes indefinitely with Supabase (Prisma v7 + Next.js)
ORMHi everyone 
I’m facing an issue with Prisma v7 in a Next.js project and I’d really appreciate some guidance.
I did not follow the full Quickstart from the Prisma docs.
Instead, I:
Created a Next.js project (create-next-app)
Installed:
npm install -D prisma@7
npm install @prisma/client@7
npx prisma init
Created a Supabase free project
Used the connection strings from Supabase “Connect” panel
My .env:
DIRECT_URL="postgresql://postgres.xxx@aws-1-eu-west-1.pooler.supabase.com:6543/postgres"
DATABASE_URL="postgresql://postgres.xxx@aws-1-eu-west-1.pooler.supabase.com:5432/postgres"
What works ?
npx prisma generate
npx prisma db push (schema sync works fine)
The problem ?
When I run:
npx prisma migrate dev --name init
The command starts… and then just hangs indefinitely.
No error, no migration applied, nothing happens. It just freezes.
So I’m forced to use db push, but that doesn’t give me migration history.
Is this likely caused by my Supabase configuration (pooler ports 5432 / 6543)?
Does Prisma Migrate require a direct connection instead of the Supabase pooler?
Any help would be greatly appreciated
I’m facing an issue with Prisma v7 in a Next.js project and I’d really appreciate some guidance.
I did not follow the full Quickstart from the Prisma docs.
Instead, I:
Created a Next.js project (create-next-app)
Installed:
npm install -D prisma@7
npm install @prisma/client@7
npx prisma init
Created a Supabase free project
Used the connection strings from Supabase “Connect” panel
My .env:
DIRECT_URL="postgresql://postgres.xxx@aws-1-eu-west-1.pooler.supabase.com:6543/postgres"
DATABASE_URL="postgresql://postgres.xxx@aws-1-eu-west-1.pooler.supabase.com:5432/postgres"
What works ?
npx prisma generate
npx prisma db push
(schema sync works fine)The problem ?
When I run:
npx prisma migrate dev --name init
The command starts… and then just hangs indefinitely.
No error, no migration applied, nothing happens. It just freezes.
So I’m forced to use db push, but that doesn’t give me migration history.
Is this likely caused by my Supabase configuration (pooler ports 5432 / 6543)?
Does Prisma Migrate require a direct connection instead of the Supabase pooler?
Any help would be greatly appreciated
