Why "enableGlobalCache" is false by default? #3462
-
|
Does anyone know...
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Probably something to do with #3403? |
Beta Was this translation helpful? Give feedback.
-
|
I think you found the answer, but the gist is that the offline mirror is an old Yarn feature (it was already there in 1.x) that very few people were aware of, despite its benefits. Given that Yarn has a sizeable usage amongst company-grade applications, I felt like enabling it by default would help make our users' deployments generally safer - and it can fairly easily be disabled if not needed.
You rely on the npm registry for your deployments, which is known for being down semi-regularly. Every time I used to notice it was down, it was because people were pinging the @yarnpkg account; meanwhile my own builds all passed. It felt like a recurrent enough problem to be worth changing the default. There are also some fringe edge cases w/ PnP, although they are somewhat unlikely to be triggered in practice.
Your cache is inside your project, so once you clone it you're no longer dependant on the network. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the answer! Is there no other way to use global cache without relying on NPM? For example, what will happen if I make hardlinks or symlinks in |
Beta Was this translation helpful? Give feedback.
-
While Yarn could create the local cache using symlinks, it would quickly become irrelevant: Git won't create hardlinks on clone, so anyone checking out the repository would use the full size. This, combined with how we can in theory benefit from copy-on-write (which is safer than hardlinks, since it doesn't run the risk of accidentally corrupting the global archives), made hardlinks not that interesting.
Where would Yarn retrieve the archives from on CI, if not the local cache? |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I get it. So to fully utilize the upside of the local cache mode in the company-grade use case, one must be using the Zero-Install workflow. Since with the |
Beta Was this translation helpful? Give feedback.
I think you found the answer, but the gist is that the offline mirror is an old Yarn feature (it was already there in 1.x) that very few people were aware of, despite its benefits. Given that Yarn has a sizeable usage amongst company-grade applications, I felt like enabling it by default would help make our users' deployments generally safer - and it can fairly easily be disabled if not needed.
You rely on the npm registry for your deployments, which is known for being down semi-regularly. Every time I used to notice it was down, it was because people were pinging the @yarnpkg account; meanwhile my own builds all passed. I…