Build Cache
A mechanism that caches already-downloaded dependency packages during the build process to accelerate subsequent builds, but which may become a vector for the propagation of malicious packages.
Timeline (last 90 days)
Vercel has added to the deployment summary feature a display of the build cache size saved in this build and how close that cache is to the limit of its build machine.
When the build cache exceeds the build machine's capacity limit, the cache is discarded outright, and the next build must start from scratch.
Build cache is the collection of intermediate artifacts that CI/CD platforms persist during the build process, typically including dependency packages, compilation outputs, framework-generated static resources and toolchain intermediate files.
The core principle of build cache is content addressing: the platform computes a hash of the inputs (source code, lock files, environment variables, etc.) and, when the same hash matches, directly reuses previously saved artifacts.
All Facts (4)
When the build cache exceeds the build machine's capacity limit, the cache is discarded outright, and the next build must start from scratch.
50%UnverifiedBuild cache is the collection of intermediate artifacts that CI/CD platforms persist during the build process, typically including dependency packages, compilation outputs, framework-generated static resources and toolchain intermediate files.
50%UnverifiedThe core principle of build cache is content addressing: the platform computes a hash of the inputs (source code, lock files, environment variables, etc.) and, when the same hash matches, directly reuses previously saved artifacts.
50%UnverifiedVercel has added to the deployment summary feature a display of the build cache size saved in this build and how close that cache is to the limit of its build machine.
50%