Hey @zakitek. I can't see the image you shared. Can you share the error details another way?

I see, ok i've updated the post.

Thanks for sharing the error message. It's not a lot of detail, so we'll need to do some things to get at the cause of the error.

You mentioned that there were no changes to the code base. I want to figure out if there's a package update or data change that could have caused the error.

• I assume something must have changed (though not necessarily the code itself) or you wouldn't have needed a new deployment. So what was it that did change between this deployment and the previous one?

• Does it work if you redeploy a previous deployment?

• Does the package.json file have specific versions pinned (e.g. "package-name": "2.0.0"), or does it allow minor version updates (e.g. "package-name": "^2.0.0")?

Hey Amygan, Thanks for your quick response. Regarding your first question, Trust me, nothing serious has changed. How do I know that? This web app is based on a boilerplate that I'm using to build two web applications. When I deployed the first one after adding some minor features, I knew right away that something was wrong with Vercel because there was no way that feature could have caused the issue. To verify that, I went to the second app, literally removed a space, and redeployed it. And guess what? It failed at the build phase just like the first one. And to further verify that, I've just redeployed a previous version (that was working just fine), and it failed as well! regarding your last question, i didn't understand. I've already shared with you a snippet of the package.json file.

Update: The build has failed on Netlify as well. I will open an issue on the Prisma repo and see what I get.

Update: I've updated Prisma client and it has, thank god, deployed successfully. Thank you.