Composer caches every package version, and vendor folders repeat them
The global cache plus a vendor folder per project means the same library many times over. What to clear and what to leave.
What fills your disk, where it hides, and what is safe to remove. Every guide gives you a way to check it on your own Mac.
The global cache plus a vendor folder per project means the same library many times over. What to clear and what to leave.
Coursier, ivy and sbt each cache separately, and every project has its own build output. Where they are and what is safe.
Package libraries, renv caches and knitted output accumulate per project and per R release. What to prune and what to keep.
Checkpoints, embedded outputs and downloaded datasets fill a data science Mac. What is derived, what is irreplaceable, and how to tell.
The ports tree, distfiles and inactive ports all accumulate. The two commands that reclaim most of it safely.
Electron, Node headers and packaged builds accumulate outside your project. Where each cache is and what prunes it.
Pretrained weights, datasets and compiled kernels land in hidden cache folders. Where each framework puts them and what is safe.
Workspaces, caches and container images pile up on a self hosted runner. What to prune automatically rather than by hand.
A profiling session can produce a multi gigabyte trace. Where they are saved and which ones are worth keeping.
Mobile style editors copy media into the project rather than referencing it. Where drafts live and what deleting one removes.
Affinity, Pixelmator and similar tools cache previews, history and scratch data. What each keeps and which folders are safe.
Why Apple removed the option, what encryption does instead, and the one case where overwriting still matters.