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
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
By default, npm install -g often has the wrong permissions and blows up. This is an npm issue, but when people encounter this problem in the course of executing npm install -g elm, they often report it as an Elm issue here. For example:
We could potentially improve this user experience by running a preinstall script to detect where npm is going to try to perform the global installation, checking the permissions on that directory, and figuring out of there's going to be a problem. If there will be, we can provide a more helpful error message than the default EACCESS explosion, and point users to the docs on how to resolve the problem.
This could not only reduce the number of misreported issues on this repo, it could also help users get npm configured properly - as opposed to their re-running the command with sudo, which is a quick but suboptimal fix.
The text was updated successfully, but these errors were encountered:
By default,
npm install -g
often has the wrong permissions and blows up. This is annpm
issue, but when people encounter this problem in the course of executingnpm install -g elm
, they often report it as an Elm issue here. For example:We could potentially improve this user experience by running a
preinstall
script to detect wherenpm
is going to try to perform the global installation, checking the permissions on that directory, and figuring out of there's going to be a problem. If there will be, we can provide a more helpful error message than the defaultEACCESS
explosion, and point users to the docs on how to resolve the problem.This could not only reduce the number of misreported issues on this repo, it could also help users get
npm
configured properly - as opposed to their re-running the command withsudo
, which is a quick but suboptimal fix.The text was updated successfully, but these errors were encountered: