Hey y’all, I have question about Prisma client being cached on Heroku: I did migration locally and run build on Heroku. App was built and then, in release tasks, migration was applied. Then, I modified my code to use newly added field and run build again. But then build failed - Heroku used cached Prisma client, and TypeScript raised error saying that field does not exist. I solved that by setting NODE_MODULES_CACHE=false, but I would prefer to cache my node modules, so the app builds faster. Is there something I can do?

I haven't had this issue when deploying to Heroku in a Node app that uses Prisma. Generally when your Heroku app rebuilds on deploy, it should be rebuilding your app-specific prisma client too

Yeah @prisma/client is dependency and prisma is devDependency

i think they both need to be dependencies, not devDependenices

Yeah… 🤷