You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the newer yarn versions, yarn automatically generates a .yarn/cache directory which is supposed to be a local cache instead of the global cache which is in yarn 1.
Should this be added to the .gitignore or be committed to the repo?
The actual issue here is that the cached packages are bloating the changed files.
Also should the yarn version be enforced, because the diff between a v1 and a v3 yarn.lock are significant. It doesn't cause any problems, but it could maybe be better to use one version on the same major version to avoid any nasty issues.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With the newer yarn versions, yarn automatically generates a
.yarn/cache
directory which is supposed to be a local cache instead of the global cache which is in yarn 1.Should this be added to the
.gitignore
or be committed to the repo?The actual issue here is that the cached packages are bloating the changed files.
Also should the yarn version be enforced, because the diff between a v1 and a v3
yarn.lock
are significant. It doesn't cause any problems, but it could maybe be better to use one version on the same major version to avoid any nasty issues.Beta Was this translation helpful? Give feedback.
All reactions