NEXTJS_NO_TURBO_CACHE
Last updated March 4, 2025
Conformance is available on Enterprise plans
This rule prevents the folder from being added to the Turborepo cache. This is important because including the folder in the Turborepo cache can cause the cache to grow to an excessive size. Vercel also already includes this cache in the build container cache.
The following config will be caught by this rule for Next.js apps:
To fix, add to the list of outputs for the task.
Was this helpful?