Anyone have cache issues when deploying to vercel? Is this normal - https://prisma.slack.com/archives/CA491RJH0/p1649384284408699?thread_ts=1649383777.709209&cid=CA491RJH0 - I followed this tutorial by the Primsa team - https://vercel.com/guides/nextjs-prisma-postgres#step-5.-set-up-github-authentication-with-nextauth

Unfortunately not right now, we are working on figuring out a way to avoid this. Vercel has some pretty aggressive caching that unfortunately leads to the postinstall hook not being run, which means that Prisma Client is not generated. The best around this is to add

npx prisma generate

(or equivalent) to one of the build commands that are run.

Thanks very much for the answer!