prisma/prisma-client-generated-cache-repro

This repository is a demonstration project that reproduces a specific caching bug affecting Prisma, a popular database toolkit, when deployed to hosting platforms like Vercel or Netlify. It exists to show developers exactly how to trigger the problem and prove that it happens, rather than to serve as a usable application. The project walks you through a step-by-step scenario. You start by setting up a simple database and deploying a basic web app to Vercel. Everything works fine at first. Then, you add a new field to your database schema, say, adding a "name" column to a user record, and update your code to use it. When you deploy the changed app a second time, the deployment fails with a confusing error. The app tries to use the new "name" field, but the deployed code is acting as if it only knows about the old structure. The fix is to force Vercel to completely clear its build cache and start fresh, which makes the error go away. The underlying issue is a mismatch between what your database looks like and what your application code expects. When you use a code generator like Prisma, it reads your database schema and creates ready-to-use code for querying it. Hosting platforms like Vercel speed up deployments by reusing previously built files from a cache. In this case, the platform serves up an old, cached version of the generated code even though your database and application code have moved on. Forcing the cache to clear rebuilds everything from scratch, syncing them back up. This project is intended for developers on the Prisma team or contributors trying to diagnose and fix this caching behavior. It provides a reliable, repeatable way to trigger the exact failure so someone can test whether a potential fix actually works. The README does not go into detail on broader context or long-term solutions, it is simply a focused guide to reproducing the bug.