npm ERR! path E:\SouthernPowerGridProject\web_project\AutoOPS\autoops\node_modules\fsevents\node_modules\dashdash\node_modules
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall scandir
npm ERR! Error: EPERM: operation not permitted, scandir ‘E:\SouthernPowerGridProject\web_project\AutoOPS\autoops\node_modules\fsevents\node_modules\dashdash\node_modules’
npm ERR! { Error: EPERM: operation not permitted, scandir ‘E:\SouthernPowerGridProject\web_project\AutoOPS\autoops\node_modules\fsevents\node_modules\dashdash\node_modules’
npm ERR! stack: ‘Error: EPERM: operation not permitted, scandir \’E:\\SouthernPowerGridProject\\web_project\\AutoOPS\\autoops\\node_modules\\fsevents\\node_modules\\dashdash\\node_modules\”,
npm ERR! errno: -4048,
npm ERR! code: ‘EPERM’,
npm ERR! syscall: ‘scandir’,
npm ERR! path: ‘E:\\SouthernPowerGridProject\\web_project\\AutoOPS\\autoops\\node_modules\\fsevents\\node_modules\\dashdash\\node_modules’ }
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\ThinkT420\AppData\Roaming\npm-cache\_logs\2017-10-30T06_50_38_610Z-debug.log
Before there are times this, thought it is really not enough permissions, feel a little strange, with administrator rights to perform, sometimes really useful, but later checked, when the cache problem, clean up the cache on the line, without administrator rights.
Method 1.
You need to delete the npmrc file.
Emphasis: not the nodejs installation directory npm module under the npmrc file
but in C:\Users\{account}\ under the .npmrc file …
Method 2.
Or just clean it up directly with the command, console type.
npm cache clean –force
added 114 packages in 42.369s
E:\SouthernPowerGridProject\web_project\AutoOPS\autoops>npm cache clean –force
npm WARN using –force I sure hope you know what you are doing.
E:\SouthernPowerGridProject\web_project\AutoOPS\autoops>npm install
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {“os”:”darwin”,”arch”:”any”} (current: {“os”:”win32″,”arch”:”x64″})
added 114 packages in 42.369s
Done!
Similar Posts:
- [Solved] npmError: EPERM: operation not permitted,…
- error An unexpected error occurred: “EPERM: operation not permitted, scandir ‘E:\\aPritice\\JDe\\e
- [Solved] Vue Project Created error: found 23 vulnerabilities (2 low, 16 moderate, 5 high)
- [Solved] NPM installation error: error: eacces: permission denied
- npm ERR! { Error: EPERM: operation not permitted, mkdir ‘D:\Program Files\nodejs\node_cache\_cacache’
- [Solved] NPM installation Vue scaffold error: npm ERR! Unexpected end of JSON input while parsing near…
- npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents
- npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: want
- ERROR EPERM: operation not permitted, mkdir ‘C:\Users\Administrator\Desktop\text\nuxt\basic\…
- After npm5, execute NPM cache clean and report an error