I tried pushing my nextJs site to vercel and it failed with some error saying: Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again. Is this not somehow done automatically, or how to do I make vercel do it? it also said check out this url, which wasn't too helpful: https://github.com/prisma/prisma-client-js/issues/390

@Ivan Lukianchuk 👋 I think you’re facing a similar issue as mentioned here so the solution might be to run

prisma generate

in a postinstall hook.

I'm still not sure exactly what to do. I've followed the links and other links and it kind of talks about postinstall but no one will just write out the 1 to 3 lines we need to use. I tried adding this: "postinstall": "npm run prisma generate" so my scripts looks like this: "scripts": {     "dev": "next dev",     "build": "next build",     "start": "next start",     "postinstall": "npm run prisma generate"   }, and I get the error: npm ERR! missing script: prisma If I add these 3 lines from someone's linked code: "generate": "npm -s run generate:prisma",     "generate😛risma": "prisma generate",     "postinstall": "npm run generate" I get this: sh: prisma: command not found I'm not a package.json expert, I usually can build things without touching it, so I'm not sure of the lifecycle or intricacies of all these build scripts, so I'm really hoping there is a simple answer here I'm just missing

"postinstall": "npx prisma generate"

This is all that’s required.

ok, let me give that a try

the only reason I got prisma was for nextJs, and every doc I or tutorial seem to follow is broken or using something outdated,

Have you followed this from the docs? It seems to work fine for me.

ok, that line seemed to do it

Vercel caches

node_modules

which is why you were facing this issue.

I’m not sure if inbetween that time you changed to add prisma versus I think it used to be add prisma/cli

That shouldn’t affect the workflow as

npx prisma

would work in either way.

hmm, well I only just pushed to a fresh vercel yesterday, so I assume it would have to add all the node modules right there, and it failed on first try, but I didn't have the postinstall hook, although is that always needed, because I never saw it in any docs

This was a recently faced issue with Vercel as a couple of other users were facing this as well.

well it would definitely be worth popping this line somewhere in the docs for future folk, or even in the error messages generated, like the one that told me to go to issue 390 I saw in the vercel logs

Yeah this will be added to the docs in the deployment guide 🙂