Npm ERR! code EPERM

Question

I'm using node v6.11.2, npm v5.3.0 and angular/cli v1.2.7.

I'm suddenly receiving the following error message for a majority of my npm installs. Never seen it before...

mmeppiel@MC-LT-MMEPPIEL MINGW64 ~/Desktop/Angular Solutions/my-app (master)
$ npm install --save [email protected] font-awesome
npm ERR! path C:\Users\mmeppiel\Desktop\Angular Solutions\my-app\node_modules\fs                            events\node_modules
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall lstat
npm ERR! Error: EPERM: operation not permitted, lstat 'C:\Users\mmeppiel\Desktop                            \Angular Solutions\my-app\node_modules\fsevents\node_modules'
npm ERR!     at Error (native)
npm ERR!  { Error: EPERM: operation not permitted, lstat 'C:\Users\mmeppiel\Desk                            top\Angular Solutions\my-app\node_modules\fsevents\node_modules'
npm ERR!     at Error (native)
npm ERR!   stack: 'Error: EPERM: operation not permitted, lstat \'C:\\Users\\mme                            ppiel\\Desktop\\Angular Solutions\\my-app\\node_modules\\fsevents\\node_modules\                            '\n    at Error (native)',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'lstat',
npm ERR!   path: 'C:\\Users\\mmeppiel\\Desktop\\Angular Solutions\\my-app\\node_                            modules\\fsevents\\node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\mmeppiel\AppData\Roaming\npm-cache\_logs\2017-08-08T00_56_                            59_442Z-debug.log

Can anyone explain what's going on here? Things I've tried:

• Running Git Bash as an administrator
• Turning off my firewall and AntiVirus protections
• Running npm cache clean
• Manually deleting the contest of AppData\Roaming\npm-cache
• Uninstalling node via the Control Panel and reinstalling
• Gave Everyone full permissions to C:\Program Files\nodejs
• Reinstalled the CLI
• Restarted my computer (can't hurt?)
• Made sure the node_modules folder is not read only

Appreciate your time!

Solution 1

Are you using any private or company registry. check your .npmrc file and make sure its available.

if you are in company environment, make sure proxy is not a problem.

check in your folder if any package-lock.json is generated. you can delete that make re install.

I have little doubt but node 6.x.x with npm 5.x.x might be a problem as node 7.x.x is compatible arable with 5.x.x. And normally node 6.x.x is compatible with npm 4.x.x

Solution 2

I get this error when running Visual Studio Code because the typescript compiler watches files and locks them (see https://github.com/Microsoft/vscode/issues/28593). The solution is to temporarily close VS Code when dealing with NPM. Perhaps you have something watching files?

Solution 3

I'm having the same problem, even using Node v8.6.0 and npm v5.4.2.

Solved with:

npm cache clean --force

&

npm install [package] --force

Reference: npm wiki's troubleshooting guide.

Solution 4

This might help https://alastaircrabtree.com/fixing-intermittant-eperm-operation-not-permitted-on-npm-install/

Also try to play with different node versions the best way of upgrading/switching your node on Windows is to use nvm-windows this way you can have multiple node versions installed on your dev machine you can switch across.

UPDATE 0:

When you dealing with such a problems you have to make sure that nothing is locking our node_modules folder like your Code Editor(e.g VS Code, ect) or you might be running npm start in another console window, etc

UPDATE 1:

If you still experiencing the issue try completely to uninstall both node and npm from your system. Then restart your machine and install node and npm again.

HOWEVER

It is seams like it is common issue by looking in to the npm issues filtering by npm ERR! code EPERM. If you browse some of these issues you will see that some people saying that switching the node version is actually help(exactly I was saying at first above) so you need to play with nvm-windows and see what node version is working best for you.

Once you have nvm-windows installed you can do:

• nvm list - shows all your local node versions you can switch to
• nvm list available - shows all actual node versions that you can install locally
• nvm install <version number> - install(download+install) a particular node version
• nvm use <version number> switch to particular node version
• nvm help - will give you help

If you jump from major version of npm some of your packages that you installed with a previous node version might no longer work so you have to be reinstall them

Solution 5

Run windows command prompt as administrator. Then navigate ("cd directoryName")to your project folder do "npm install".

View more solutions