Updating the Prisma saga: it’s 2.15 release fixes the EPIPE issue but as @pi0neerpat notes 2.13+ now has migrate dev which can make it dificult to run a cloud db like Supabase or Heroku as a dev database because with Prisma’s “shadow database” the db user must have permissions to create databases (something your Heroku user will not have). Prisma intends to addresss that issue in via this approach probably in 2.16.
That said, since moving to 2.15 I haven’t experienced the EPIPE socket issue at all.