Skip to content

Conversation

MartijnHols
Copy link

The yarn-cache directory will grow infinitely big if it is restored every run and never cleared. A large cache will slow down builds, and might lead to increased storage costs. GitHub also offers no way to manually purge the cache, so there is no manual workaround either.

I choose weekly since I figured it's long enough have cache hits for most builds, but not too long for the cache to grow gigantic.

The yarn-cache directory will grow infinitely big if it is restored every run and never cleared. A large cache will slow down builds, and might lead to increased storage costs. GitHub also offers no way to manually purge the cache, so there is no manual workaround either.

I choose weekly since I figured it's long enough have cache hits for most builds, but not too long for the cache to grow gigantic.
@MartijnHols MartijnHols closed this Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant