Consider caching `node_modules` for jobs that run `yarn install` instead of using artifacts
In !29341 (merged), we started to cache node_modules
instead of caching .yarn-cache
and retrieving node_modules
from artifacts as this seems to have better performance overall.
Given the cache key definition:
cache:
key:
files:
- yarn.lock
- config/webpack.vendor.config.js
prefix: "v2"
paths:
- node_modules/
it should be safe from a data expiration point of view to cache node_modules/
.