You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the OS tmp directory for Jest's ephemeral generated assets means that most CIs can't reliably cache it and keep test runs consistently fast.
Using a default cacheDirectory like node_modules/.jest-cache would stash away those files in a spot that most (if not all) devs have git-ignored and workspace-ignored by default, but also remain completely cacheable by container-based CI services like Travis.
The text was updated successfully, but these errors were encountered:
cacheDirectory is configurable for this reason. We used to store it inside of Jest but it was always a huge issue to people so we changed to a temp folder. Please configure Jest the way you like for your CI :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Using the OS tmp directory for Jest's ephemeral generated assets means that most CIs can't reliably cache it and keep test runs consistently fast.
Using a default cacheDirectory like
node_modules/.jest-cache
would stash away those files in a spot that most (if not all) devs have git-ignored and workspace-ignored by default, but also remain completely cacheable by container-based CI services like Travis.The text was updated successfully, but these errors were encountered: