Npm install error EPERM Operation not permitted

Troy Bryant picture Troy Bryant · Dec 12, 2017 · Viewed 27k times · Source

So when trying to run the angular4 project today my first error was : npm install eperm operation not permitted so I thought to delete my node modules folder and retry. But running npm install I am running in to this error npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start". I've closed vscode to try and run the install to make sure nothing was locking it. I've tried npm cache clean but results in errors.enter image description here

Todays latest struggles :

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-
  cli.js',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   '@angular/cli@latest' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session 2a0bb102467943cf
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 error cb() never called!

Admin Results: enter image description here

Any suggestions?

My package.json looks like this :

{
 "name": "gamemanagement",
 "version": "0.0.0",
 "license": "MIT",
 "scripts": {
   "ng": "ng",
   "start": "ng serve",
   "build": "ng build",
   "test": "ng test",
   "lint": "ng lint",
   "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
  "@angular/animations": "^5.0.1",
  "@angular/cdk": "^5.0.0-rc0",
  "@angular/common": "^5.0.1",
  "@angular/compiler": "^5.0.1",
  "@angular/compiler-cli": "^5.0.1",
  "@angular/core": "^5.0.1",
  "@angular/forms": "^5.0.1",
  "@angular/http": "^5.0.1",
  "@angular/material": "^5.0.0-rc0",
  "@angular/platform-browser": "^5.0.1",
  "@angular/platform-browser-dynamic": "^5.0.1",
  "@angular/platform-server": "^5.0.1",
  "@angular/router": "^5.0.1",
  "@ng-bootstrap/ng-bootstrap": "^1.0.0-beta.5",          
  "angular2-moment": "^1.7.0",
  "angular2-text-mask": "^8.0.4",  
  "angularfire2": "5.0.0-rc.3",
  "ap-angular2-fullcalendar": "^1.3.5",
  "bootstrap": "4.0.0-beta",
  "core-js": "^2.4.1",
  "firebase": "4.6.2",
  "font-awesome": "^4.7.0",
  "jquery": "^3.2.1",
  "moment": "^2.19.3",
  "ng2-date-picker": "^2.6.2",              
  "popper.js": "^1.12.9",
  "rxjs": "^5.4.2",
  "sweetalert2": "^7.0.9",
  "typescript": "^2.6.1",
  "zone.js": "^0.8.14"
 },
"devDependencies": {
"@angular/cli": "^1.5.3",
"@angular/compiler-cli": "^4.2.4",
"@angular/language-service": "^4.2.4",
"@types/jasmine": "~2.5.53",
"@types/jasminewd2": "~2.0.2",
"@types/node": "~6.0.60",
"codelyzer": "~3.2.0",
"jasmine-core": "~2.6.2",
"jasmine-spec-reporter": "~4.1.0",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.1.2",
"ts-node": "~3.2.0",
"tslint": "~5.7.0",
"typescript": "~2.3.3"
}

}

Answer

svoychik picture svoychik · Dec 13, 2017

I had the same issue. After cache clean and updating npm everything is ok. So try to run:

npm cache clean --force

npm install -g npm@latest