'Error: EPERM: operation not permitted, unlink 'D:\Sources\**\node_modules\fsevents\node_modules\abbrev\package.json'

I just updated npm to 5.4.0.
Now, Whenever I want install a npm package I get the following error:

D:\Sources\DownloadCms\Md.Download\Web.Angular>npm install mds.angular.datetimepicker@latest --save
npm ERR! path D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json'
npm ERR!     at Error (native)
npm ERR!  { Error: EPERM: operation not permitted, unlink 'D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.jso
n'
npm ERR!     at Error (native)
npm ERR!   stack: 'Error: EPERM: operation not permitted, unlink \'D:\\Sources\\DownloadCms\\Md.Download\\Web.Angular\\node_modules\\fsevents\\node_modules\\ab
brev\\package.json\'\n    at Error (native)',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'D:\\Sources\\DownloadCms\\Md.Download\\Web.Angular\\node_modules\\fsevents\\node_modules\\abbrev\\package.json' }
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\Mohammad\AppData\Roaming\npm-cache\_logs\2017-09-03T03_25_50_432Z-debug.log

I'm dead sure, run CMD as administrator.

Also I checked D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json\, package.json is not exist in path !

Edit: Upgrade to v5.4.1, still get the same error, even cannot work around with --no-optional :-(

npm package.json

Solution 1:^[1]

I was able to fix this by running the command prompt/bash as admin and closing VSCode! Seems like VSCode was locking some files. Potentially something else could be locking these files for you.

Solution 2:^[2]

If you downgrade to 5.3 and still get the same error in Windows like me.
After hours working with npm versions I found the following solution:

1. Download latest recommended version of nodejs, these days is node-v6.11.3-x64
2. Uninstall nodejs with it.
3. Go to C:\Users\{YourUsername}\AppData\Roaming folder and delete npm and npm-cache folders
4. Run installer of nodejs again and install it
5 Update npm to 5.3 with npm i -g [email protected] command line

Now you should use npm without any issues.

Solution 3:^[3]

Please close all IDE like visual studio code. run npm install command through node.js command prompt. Enjoy !

Solution 4:^[4]

cache clean and npm update to latest with force work for me

npm cache clean --force

npm install -g npm@latest --force

Solution 5:^[5]

I fixed by downgrading npm from 5.4.0 to version 5.3

npm i -g [email protected]

I Hope this helps for you

Solution 6:^[6]

I tried this solution found at a How to fix Node.js blog

just use

npm cache clean

in windows if it refuses use

npm cache clean --force

Solution 7:^[7]

I had the same problem on Windows.

The source of the problem is simple, it is access permission on folders and files.

In your project folder, you need

After cloning the project, change the properties of the folder and change the permissions of the user (give full access to the current user).
Remove the read-only option from the project folder. (Steps 1 and 2 take a long time because they are replicated to the entire tree below).
Inside the project folder, reinstall the node (npm install reinstall -g)
Disable Antivirus. (optional)
Disable Firewall. (optional)
Restart PC.
Clear the npm cache (npm clear)
Install the dependencies of your project (npm install)

After that, error "Error: EPERM: operation not permitted, unlink" will no longer be displayed.

Remember to reactivate the firewall and antivirus if necessary.

Solution 8:^[8]

I had the same issue and all I needed to do was login to npm

npm login

or alternatively

npm add user // consult the documentation for the params

Solution 9:^[9]

If all of the above failed to work for you, you might want to

restart your system
run command prompt as admin
run the npm command

Solution 10:^[10]

In my case, the problem was that, I did not install typescript. Although I did install Node and Angular. To check if you have installed typescript or not

Run this command: tsc -v

If not, then to install typescript

Run this command: npm install -g typescript

And, finally to install required dependencies

Run this command: npm install

in the root folder of the project.

---- Hope this helps someone ----

Solution 11:^[11]

For those who are coming from Windows OS, you just need to stop the development server and then execute your npm install ... command.

It is strange how Windows doesn't allow installing dependencies while server is running, but MacOS does allow. If this doesn't work, then only go for the other options - clean cache, downgrade nodejs etc.

Solution 12:^[12]

I had this logs in Windows. I did the following

Close Visual Studio Code
Run Command Line as admin

Solution 13:^[13]

Deleting package-lock.json fixed it for me.

Solution 14:^[14]

I'm using VsCode and solved this issue by stopping the application server and them run npm install. There are files that were locked by the application server.

No need to close the IDE, just make sure there's no another process locking some files on your projects.

Solution 15:^[15]

For me it worked in bash from git package try:

C:\Program Files\Git\bin\bash.exe

then:

npm install mds.angular.datetimepicker@latest

Solution 16:^[16]

There seems to be many solutions out there that worked with downgrading npm versions. For me, the solution was

npm install -force

I tried the downgrading of npm versions, modifying my npm prefix config to match the npm directory, and clearing cache. None of these worked, but apparently they worked for others, so it may be worth a shot.

Solution 17:^[17]

For me on Windows the problem was too long path length. I moved the project to a smaller length path and it worked.

Solution 18:^[18]

Mine was as a result of opening my project folder a 2 different terminals. I solved it by closing all running terminal (vs code was excluded) and executing the installation command again.

I hope this helps someone.

NB: deleting node_modules didn't solve it.

Solution 19:^[19]

Deleting my node modules folder and running a normal npm install did it for me

Solution 20:^[20]

For me it was Docker...

The moment that I closed the app container, I could do an npm install without any proble

P.S My node version is 14.15.5

Solution 21:^[21]

I fixed this by removing the dist folder

--- Remove dist or public folder

Solution 22:^[22]

the same error comes to me when i update the npm version to the latest 5.4 downgrade to the version 5.3.0 is useful.the error comes from the npm 5.4,you can check it in the issuses in npm 5.4

npm install [email protected] -g

Solution 23:^[23]

Fixed in NPM 5.6.0

Upgrade to NPM 5.6.0 solved problem for me.

Solution 24:^[24]

I wanted to run npm install from within my external hard drive as this is where i saved my code workspace. Windows 10 OS.

But I was getting the same error as the original post.None of the previous answers worked for me, I tried all of them:

uninstalling nodejs then re-installing
uninstalling nodejs then downgrading/installing a lower version of nodejs.
npm install -force
deleting the folders from C:\Users{YourUsername}\AppData\Roaming ... npm and npm-cache then re-installing.
npm cache clean --force
npm cache clean
npm install --g or npm install --global

What worked for me was this:

copy the folder from C:\Program Files\nodejs to D:\Program Files\nodejs
Then go to Control Panel\System and Security\System
Advanced System Settings
Environment Variables
System Variables
Double click Path
Add a new path
D:\Program Files\nodejs
Click ok
restart PC.
try npm install from within D: Drive

Solution 25:^[25]

npm cache verify solved my issue. I was doing: ng new my-app and I faced similar error

I have node version: 10.16.0
npm v 6.9.0

Solution 26:^[26]

After trying everything, including node/npm upgrade, cache cleaning and reverting code, nothing helped besides one simple thing: Turning OFF Windows 10's Real-time protection during the dev/build. Looks like latest updates made it super aggressive.

Solution 27:^[27]

npm login is required before publish

Solution 28:^[28]

For windows,

Download latest recommended version of nodejs, these days is node-v6.11.3-x64
Uninstall nodejs with it.
Go to C:\Users\{YourUsername}\AppData\Roaming folder and delete npm and npm-cache folders
Run installer of nodejs again and install it
By default npm 3.10.10 should be installed along with node-v6.11.3-x64.
It worked for me with npm 3.10.10 but did not work with 5.3.X. Also it did not worked with higher versions of node (above node-v6.11.3-x64)

Solution 29:^[29]

My problem was executing the command (npm audit fix all). I solved it when closing VSCODE and re-executed the command without problems.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	Mark Whitfeld
Solution 2
Solution 3	jagdish desai
Solution 4	DeC
Solution 5	Mohammad Dayyan
Solution 6	Chris Ihure
Solution 7	Thiago Silva
Solution 8	frzsombor
Solution 9	jed
Solution 10
Solution 11
Solution 12	MJ Montes
Solution 13	Dean
Solution 14	Ermenegildo Cumbe
Solution 15	Adrian
Solution 16	JohnsonCore
Solution 17	nAviD
Solution 18	Otis-iDev
Solution 19	phunder
Solution 20	air_ioannis
Solution 21	Pir Abdul
Solution 22
Solution 23	ptilton
Solution 24	ivsuleman
Solution 25	adiga
Solution 26	David D.
Solution 27	blazehub
Solution 28	arsho
Solution 29	Juan Carlos Aponte

'Error: EPERM: operation not permitted, unlink 'D:\Sources\**\node_modules\fsevents\node_modules\abbrev\package.json'

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]

Solution 23:[23]

Solution 24:[24]

Solution 25:[25]

Solution 26:[26]

Solution 27:[27]

Solution 28:[28]

Solution 29:[29]