My current setup involves Prisma and Vercel. While Prisma generates the client dynamically, I've noticed that Vercel tends to cache the old client version and only rebuilds it after redeploying or making significant changes through its interface.
I'm looking for a way to ensure that a specific package, such as the Prisma client in this case, gets rebuilt every time I push changes to GitHub. I know changing the package version triggers a rebuild, but I'm wondering if there's a more efficient method rather than resorting to this workaround. Is there, perhaps, a special flag or setting that can be used to prevent caching of "@prisma/client" and force a rebuild automatically?
"@prisma/client": "3.8.0" // is there a unique flag to avoid caching?