Can I purge old and outdated cache files?

Feature request

On out CI system we upload webpack’s cache to a storage after each build and download them on the next build to speed up build.

After about 6 months, we find there is a 800MB cache directory with more than 100 .pack files in this cache, causing slower and slower download time.

What is the expected behavior?

We’d like to see an API to purge outdated cache content from these files, we can then run purge monthly, a slow purge process is acceptable since this runs only once per month.

What is motivation or use case for adding/changing the behavior?

Try to limit cache size in long term.

How should this be implemented in your opinion?

Maybe we should have a {purge: true} in cache configuration

Are you willing to work on this yourself?

Not able to do that

[sokra]

Perhaps we can include cache outdated information in output stats

You can set infrastructureLogging: { level: "verbose" } to get a few more lines of logging about the caching.

On short term we want to fix the cache issue by removing all unused files from the cache directory after writing the cache. That sounds easy but actually it a bit tricky since, due to lazy deserialization of the cache, we don’t know all files that are currently in use. We might change the cache format a little bit to know these details.

[Gavin-Gong]

Is there any progress on this issue?