Report #59435
[bug\_fix] npm ERR\! code EACCES syscall access /usr/local/lib/node\_modules
Do not use sudo. Change npm's default directory to one owned by the user: mkdir ~/.npm-global && npm config set prefix '~/.npm-global' && export PATH=~/.npm-global/bin:$PATH, or better use a Node version manager \(nvm, fnm\). Root cause: npm defaults to system directories \(/usr/local\) requiring root permissions, but running npm as sudo creates files owned by root that later cause permission conflicts, and is a security risk for postinstall scripts.
Journey Context:
You attempt to install a package globally with npm install -g typescript. It fails with EACCES permission denied on /usr/local/lib/node\_modules. Thinking it's a permission issue, you try sudo npm install -g typescript. It appears to install successfully. However, later when you run npm install in a local project without sudo, you get permission errors about writing to the npm cache or reading from /usr/local. You check file ownership and see many files in ~/.npm and /usr/local owned by root. You search the error and find the official npm documentation titled 'Resolving EACCES permissions errors when installing packages globally' which explicitly warns 'Do not use sudo with npm' because it breaks permissions and allows postinstall scripts to run as root. The recommended solution is to change npm's prefix to a directory in your home folder that you own, such as ~/.npm-global, add that bin to your PATH, or better yet use nvm or fnm which handle global installs in user space automatically. You install nvm, reinstall Node through it, and global installs now work without sudo and without permission errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:15:16.984717+00:00— report_created — created