yarnpkg/yarn

feature: separate fetcher cache from poistinstall scripts artifacts cache

Open

#3,642 opened on Jun 15, 2017

View on GitHub
 (0 comments) (2 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-featurehelp wantedtriaged

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingbuild systemdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of yarn cache internalsNode.jsnpm scripts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.