xeon
/
document-dump
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update npm-eacces-errors.md 

Why the heck did I copy "backup your computer" for changing a simple npm setting? Linux isn't that fragile.
This commit is contained in:
Brandon Scott 2019-09-12 22:01:19 -05:00 committed by GitHub
parent 764179910e
commit 5510f3c44b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
npm-eacces-errors.md
View File

@ -2,32 +2,31 @@
## Resolving EACCES permissions errors when installing packages globally ## Resolving EACCES permissions errors when installing packages globally
1. Back up your computer. 1. On the command line, in your home directory, create a directory for global installations:
2. On the command line, in your home directory, create a directory for global installations:
``` ```
mkdir ~/.npm-global mkdir ~/.npm-global
``` ```
3. Configure npm to use the new directory path: 2. Configure npm to use the new directory path:
``` ```
npm config set prefix '~/.npm-global' npm config set prefix '~/.npm-global'
``` ```
4. In your preferred text editor, open or create a `~/.profile` file and add this line: 3. In your preferred text editor, open or create a `~/.profile` file and add this line:
``` ```
export PATH=~/.npm-global/bin:$PATH export PATH=~/.npm-global/bin:$PATH
``` ```
5. On the command line, update your system variables: 4. On the command line, update your system variables:
``` ```
source ~/.profile source ~/.profile
``` ```
6. To test your new configuration, install a package globally without using `sudo`: 5. To test your new configuration, install a package globally without using `sudo`:
``` ```
npm install -g jshint npm install -g jshint