We've disabled Turbopack's persistent build cache specifically on Vercel to resolve OOM (Out of Memory) errors during production builds. It turns out that restoring the large cached filesystem between deployments was exceeding the memory limits of our build environment. This change ensures stable deployments while maintaining build speed, and keeps the default caching behavior for other environments like Docker and EC2. Building on Vercel

Disabled persistent Turbopack cache for Vercel builds - subh05sus/sparkmentis-fork