Unable to install nodemon Win 10?

Unable to install nodemon Win 10?
0

#1

Hi.

Please help… I have an issue I am trying to work through the very good FFC youTube video entitled : Full Stack Web App using Vue.js & Express.js: Part 1 - Intro.

I am trying to install nodemon via npm.

I am getting the following error:

$ npm install -g nodemon
C:\Users\RiCK\AppData\Roaming\npm\nodemon -> C:\Users\RiCK\AppData\Roaming\npm\node_modules\nodemon\bin\nodemon.js
npm ERR! path C:\Users\RiCK\AppData\Roaming\npm\node_modules\nodemon\node_modules\fsevents\node_modules\aproba\package.json
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall lstat
npm ERR! Error: EPERM: operation not permitted, lstat 'C:\Users\RiCK\AppData\Roaming\npm\node_modules\nodemon\node_modules\fsevents\node_modules\aproba\package.json'
npm ERR!     at Error (native)
npm ERR!  { Error: EPERM: operation not permitted, lstat 'C:\Users\RiCK\AppData\Roaming\npm\node_modules\nodemon\node_modules\fsevents\node_modules\aproba\package.json'
npm ERR!     at Error (native)
npm ERR!   stack: 'Error: EPERM: operation not permitted, lstat \'C:\\Users\\RiCK\\AppData\\Roaming\\npm\\node_modules\\nodemon\\node_modules\\fsevents\\node_modules\\aproba\\package.json\'\n    at Error (native)',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'lstat',
npm ERR!   path: 'C:\\Users\\RiCK\\AppData\\Roaming\\npm\\node_modules\\nodemon\\node_modules\\fsevents\\node_modules\\aproba\\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\RiCK\AppData\Roaming\npm-cache\_logs\2017-09-06T21_55_39_505Z-debug.log

I cant add the debug log on this post (too many characters… i’ll try to reply the log to this thread.

I have googled this loads, and am really struggling to continue. Any help or suggestions will br greatly recieved…

Thanks in advance…


#2

According to this thread,

Try turning off your anti-virus software.


#3

If you are using any command-line interface programs like Command Prompt, Powershell, Git Bash or Cmder, then you have to open them with administrative priviliges and then run your command.

Right click and choose “Run as administrator”.

Hopefully, it will solve the problem.