Skip to content
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.

Sign up for GitHub

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

Jump to bottom

More user-friendly error when failing to install binaries globally due to lack of permission #1578

Closed
dandv opened this issue Oct 31, 2016 · 1 comment
Closed

More user-friendly error when failing to install binaries globally due to lack of permission #1578

dandv opened this issue Oct 31, 2016 · 1 comment

Comments

@dandv
Copy link

dandv commented Oct 31, 2016 •
edited
Loading

Do you want to request a feature or report a bug?

Bug related to #630

What is the current behavior?

When installing packages globally, if the current user doesn't have the appropriate permissions, yarn will fail with An unexpected error occured, please open a bug report with the information provided in "~/.yarn-config/global/yarn-error.log".

If the current behavior is a bug, please provide the steps to reproduce.

On a typical Ubuntu instance when the user doesn't have superuser permissions, run yarn global add without sudo, e.g. yarn global add lighthouse.

The useful error message can only be found at the very end of the log file:

Trace: Error: EACCES: permission denied, symlink '../../home/dandv/.yarn-config/global/node_modules/.bin/chrome-debug' -> '/usr/bin/chrome-debug'
at Error (native)

What is the expected behavior?

A more easily actionable error message reminding the user about the lack of permissions.

Please mention your node.js, yarn and operating system version.

Node v6.9.1, yarn 0.16.1 on Ubuntu 16.04.1.
sebmck pushed a commit that referenced this issue Nov 1, 2016
Nicer permission errors when trying to write global binaries - fixes #…
399323c 
…1578
@sebmck
Copy link
Contributor

sebmck commented Nov 1, 2016

Created #1592 to fix this, pending approval.

@sebmck sebmck closed this as completed Nov 1, 2016
sebmck pushed a commit that referenced this issue Nov 2, 2016
Nicer permission errors when trying to write global binaries - fixes #…
6e5c065 
…1578 (#1592)
Jessidhia pushed a commit to Jessidhia/yarn that referenced this issue Nov 4, 2016
Merge branch 'master' into npm4-prepublish
fda0ecf 
* 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)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dandv @sebmck