yarnpkg/yarn

feature: separate fetcher cache from poistinstall scripts artifacts cache

Open

#3,642 创建于 2017年6月15日

在 GitHub 查看
 (0 评论) (2 反应) (0 负责人)JavaScript (41,514 star) (2,731 fork)batch import
cat-featurehelp wantedtriaged

描述

Do you want to request a feature or report a bug? feature to mitigate bugs

What is the current behavior?

We have quite a lot of issues happening at the install scripts phase of installation and some of them are related to possible cache issues (e.g. issues with node-sass).

We should have a separate cache folder for build artifacts which we could control independently from the packages cached after fetching, e.g. we could make changes in node version, application path and Yarn version to invalidate those caches.

贡献者指南

技术栈
javascriptnodejs
领域
toolingbuild systemdeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of yarn cache internalsNode.jsnpm scripts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate the current cache implementation in yarn, particularly the fetcher cache and the postinstall scripts artifacts cache. Look at the code that manages cache invalidation (node version, app path, Yarn version). Design a solution to separate these two caches, ensuring backward compatibility. Consult related issues like #3485 for context on node sass caching problems.