Yarn: Yarn caches should be invalidated when switching versions
Do you want to request a feature or report a bug?
feature
What is the current behavior?
We sometimes introduce changes to cache logic which make cache from previous version incompatible with the next one.
What is the expected behavior?
Yarn should ignore caches generated by another version.
bestander
👍2
All 5 comments
This has been the solution for most issues posted. yarn cache clean.
torifat
on 25 Nov 2016
Perhaps we should version the cache, and clear it if the version doesn't match (similar to how lockfiles are versioned). So, the current cache would have a version of 1, then we'd bump it to 2 if any breaking changes are made.
Daniel15
on 26 Nov 2016
👍3
It would require some discipline but I agree with you, @Daniel15
bestander
on 27 Nov 2016
👍1
Bootcamped the issue
bestander
on 21 Feb 2017
Done!
bestander
on 2 Mar 2017
Was this page helpful?
0 / 5 - 0 ratings
Related issues
whitecolor
路
96Comments
donaldpipowitch
路
75Comments
carlosduclos
路
86Comments
MichelDiz
路
80Comments
jmorrell
路
93Comments
Most helpful comment
Perhaps we should version the cache, and clear it if the version doesn't match (similar to how lockfiles are versioned). So, the current cache would have a version of
1, then we'd bump it to2if any breaking changes are made.