-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize persistent cache strategy #1208
Comments
有进展吗?我非常关心该功能 |
正在实现中,会优先支持 |
Merged
可设置 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problem does this feature solve?
Currently when lockfile is changed, all cache will be invalidated. For some dependencies like components, they could be changed frequently, so Farm need to support configuring that if some packages are changed, only caches of these packages are invalidated, caches of other packages should be reused.
What does the proposed API look like?
loose: boolean
, when keys like lockfile changed withloose: true
, all cache should not be invalidated, and Farm should validate cache for immutable modules.The text was updated successfully, but these errors were encountered: