-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache folder in home folder is getting backed up on macOS #1637
Comments
sebmck
pushed a commit
that referenced
this issue
Nov 3, 2016
Created #1638 to fix this, pending approval. |
sebmck
pushed a commit
that referenced
this issue
Nov 3, 2016
Thank you! |
Jessidhia
pushed a commit
to Jessidhia/yarn
that referenced
this issue
Nov 4, 2016
* master: (66 commits) Add --no-bin-links flag - fixes yarnpkg#929 (yarnpkg#1651) Add option to change the prefix of the global bin folder - fixes yarnpkg#630 (yarnpkg#1654) patterns -> filteredPatterns Add helpful nudge to yarnpkg/rfcs on issue template (yarnpkg#1650) Change reporter.log to console.log in generate-lock-entry command - fixes yarnpkg#644 (yarnpkg#1652) Fixed add command flag (yarnpkg#1653) Nested executables fix (yarnpkg#1210) Added short-flags for yarn add (yarnpkg#1618) Add name lookups to ls command - fixes yarnpkg#1599 (yarnpkg#1643) Disable flaky secureUrl test (yarnpkg#1644) Add unit tests for `yarn why`. (yarnpkg#1544) Refine flow type for config.generateHardModulePath (yarnpkg#1642) Use ~/Library/Caches as default cache location on OSX - fixes yarnpkg#1637 (yarnpkg#1638) Update aliases.js (yarnpkg#1635) Update aliases.js (yarnpkg#1634) Add webhook to archive AppVeyor build artifacts (yarnpkg#1631) Attempt to fix failing Circle CI builds (yarnpkg#1629) Adding 'yarn global upgrade'(Issue yarnpkg#776) (yarnpkg#1616) Show error message in stdout. (yarnpkg#1502) Nicer permission errors when trying to write global binaries - fixes yarnpkg#1578 (yarnpkg#1592) ...
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
What is the current behavior?
yarn creates
~/.yarn-cache/
folder, which is getting backed up automatically by macOS's Time Machine, which unnecessarily bloats the backups.What is the expected behavior?
Yarn could use
~/Library/Caches/…
to store its cache. This is the usual location for caches on macOS, and the system avoids unnecessarily backing it up.Please mention your node.js, yarn and operating system version.
yarn 0.16.1, node v6.9.0, macOS 10.11.6
The text was updated successfully, but these errors were encountered: