pub const CACHES_LONG: &str = "\
Find every package-manager cache and store on the machine, size each one, and print \
the command that clears it — largest first, with a total. On its own it deletes \
nothing, and nothing that runs on a schedule ever will: a cache is shared by every \
repository, so no single lockfile can prove its contents recoverable, which is the \
bar every dev-prune deletion has to clear. Clearing one also turns the next `devp \
restore` into a download.
`devp caches clear <manager>` runs the command this table prints, after showing you \
what goes and asking.
`--volume V:` (or `--drive`, or `--volume /mnt/data`, or any path on the one you \
mean) narrows the whole report to the caches that sit on one drive, and the \
unfiltered table gains a line breaking the total down the same way. On a machine \
whose projects live on a second disk, 22 GiB of caches is not the figure that \
decides anything — the two gigabytes on the drive that is full is.
Covered: npm, pnpm, yarn, bun, uv, pip, conda, cargo, go, maven, gradle, nuget, vcpkg, \
conan, ccache, sccache, composer, cocoapods, hex, bundler, dart, swift, terraform, \
poetry, pdm, playwright, puppeteer, huggingface, cypress, electron and deno. \
Each manager is asked where its cache is (`npm \
config get cache`, `go env GOMODCACHE`, …) rather than assumed, with read-only queries \
run from your home directory; a manager that is not installed falls back to the \
conventional location, because a cache left behind by an uninstalled manager is \
exactly the multi-gigabyte directory nobody remembers.";