-
-
Notifications
You must be signed in to change notification settings - Fork 750
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
Update README for cp... permission denied
errors for /usr/local/lib/node_modules/npm
#722
Comments
The README does already touch on this, but does not mention permission errors. I see my explanation in #478 has had a some likes so maybe the README should be clearer about what why it is needed.
|
@shadowspawn
Other than that the README looks great! Thanks for the quick change. I'm going to try selling my teammates in my company to use the n npm package to switch Node versions rather than nvm or other solutions. It's so much easier. Thanks for your development on this! |
|
Thanks @shadowspawn . You can close this issue. I'll let you know if it persists with other people. |
had this issue on a fresh macbook m2 setup, installed via homebrew. The four lines fixed it. Didn't see it in the readme, so maybe still worth adding... Thx! |
I opened a PR to expand the coverage in the README: #790 |
Problem
Permission errors in terminal on my Mac after installing the n npm package and running
n lts
.Short Version
Can I submit a PR to merge into develop branch to updated README to explain permission problem fix that appear in terminal after installing the n npm package and running
n lts
?Long Version
Issue was before in a closed issue:
#478
I experienced multiple
Permission denied
errors on my Mac (macOS Big Sur) like below in a number of folders like the example below after install the npm package and doingn lts
in my terminal:Can I submit a PR to merge into develop with instructions on how to Fix Permission Errors in a Mac? This will include running the code below in your terminal:
Configuration Details
The text was updated successfully, but these errors were encountered: