npm install give Error: EPERM, unlink

Question

using command npm install give the following error

Error: EPERM, unlink

System info: Bower version: 1.3.12 Node version: 0.10.35 OS : Windows8

I tri

Answer 1

You don't have the permissions necessary to remove that file. Somehow you have caused npm/bower to do things that conflict with the default windows permission system.

It would probably be simplest to remove bower and npm and reinstall them, and then update your npm to the latest version following the instructions here https://github.com/npm/npm/wiki/Troubleshooting

For a quick fix that might help, try this in a CMD window (you may need to start it as Administrator):

 cd C:\users\path\temp
 cacls . /T /E /C /G Everyone:F

That grants Everyone Full Control over your temp directory, which is potentially a security risk. However, it should make it possible for npm and bower to clean up old files.

I recommend you try reinstalling node, npm, and bower.

Answer 2

In my case, it was permissions - probably in the node_modules tree, but just to be sure, I granted myself ownership and rights to the entire project tree which fixed the problem.

Right click on your project folder, select Properties, then the Security tab and click the Advanced button. Set yourself as the owner and grant yourself full permissions. Check "Replace all child object permission..." and OK.

Answer 3

Had a similar issue - npm install had worked fine for months, but we upgraded a few libraries and started getting the same error.

Ended up switching from NPM to yarn, which did work.

Answer 4

What I tried

• delete node_modules folder
• delete package-lock.json
• run npm clear cache --force
• undo if the files in the folder are read-only

• run npm i again worked

Answer 5

For me, remove the indexation has solved my problem.

But the indexation was back after to have recreate the folder. In this case the solution is one the options follow:

• disable permanently the indexation service or
• exclude the folder of indexation or
• exclude the file format in indexation option.

I am on Windows 10 and this action seems resolve my problem permanently.

Answer 6

My case was even simpler... a process was still using one of the files in the folder that required deletion. Killing the task responsible enabled me to install correctly.