4399 error Error: EPERM: operation not permitted, unlink 'C:\Users\deven\AppData\Roaming\npm\node_modules.staging\tmp-5fcc012e\README.md' 4399 error { Error: EPERM: operation not permitted, unlink 'C:\Users\deven\AppData\Roaming\npm\node_modules.staging\tmp-5fcc012e\README.md' 4399 error cause: 4399 error { Error: EPERM: operation not permitted, unlink 'C:\Users\deven\AppData\Roaming\npm\node_modules.staging\tmp-5fcc012e\README.md' 4399 error errno: -4048, 4399 error code: 'EPERM', 4399 error syscall: 'unlink', 4399 error path: 'C:\Users\deven\AppData\Roaming\npm\node_modules\.staging\tmp-5fcc012e\README.md' }, 4399 error stack: 'Error: EPERM: operation not permitted, unlink \'C:\Users\deven\AppData\Roaming\npm\node_modules\.staging\tmp-5fcc012e\README.md\'', 4399 error errno: -4048, 4399 error code: 'EPERM', 4399 error
syscall: 'unlink', 4399 error path: 'C:\Users\deven\AppData\Roaming\npm\node_modules\.staging\tmp-5fcc012e\README.md', 4399 error parent: '@angular/cli' } 4400 error The operation was rejected by your operating system. 4400 error It's possible that the file was already in use (by a text editor or antivirus), 4400 error or that you lack permissions to access it. 4400 error 4400 error If you believe this might be a permissions issue, please double-check the 4400 error permissions of the file and its containing directories, or try running 4400 error the command again as root/Administrator (though this is not recommended). 4401 verbose exit [ -4048, true ]
-
1Permission issue - launch the command promt as a admin - right click on your cmd.exe and run as administrator and try .xan_z– xan_z2018-10-31 16:01:40 +00:00Commented Oct 31, 2018 at 16:01
-
2Hi @devendra, welcome to StackOverflow. It's worth reading the "How can I write a good question?" guide seen here (stackoverflow.com/help/how-to-ask). Your question here provides the error which is good, but there's a lot more information you could provide to make it easier to get to an answer. Checkout the guide for more info.Elliot Blackburn– Elliot Blackburn2018-10-31 16:08:02 +00:00Commented Oct 31, 2018 at 16:08
-
hey, i am launching cmd as admin but still get the issue.devendra– devendra2018-10-31 16:39:27 +00:00Commented Oct 31, 2018 at 16:39
9 Answers
Since you're using Windows, you have to launch the terminal as administrator and retry should work.
2 Comments
It seems like this is a problem with npm. Try deleting your node_modules folder and running npm install again. This should fix the problem.
1 Comment
Okay, for me running as the administrator did not work at all. Nothing worked until I went into my root/global folder as shown below:
C:\Users\MyName
and in that folder I deleted the node_modules folder and any Angular config files that were globally put there. After doining that I went back to my local folder and it worked perfectly.
I hope this helps.