npm install 报错（npm ERR! errno -4048，Error: EPERM: operation not permitted,）解决方法

最新推荐文章于 2025-06-06 23:28:42 发布

原创最新推荐文章于 2025-06-06 23:28:42 发布 · 4.7k 阅读

2 ·

CC 4.0 BY-SA版权

Node.js 专栏收录该内容

1 篇文章

订阅专栏

首先遇到这种问题是分两种用户，一种是windows操作系统，另一种是苹果电脑的用户

苹果用户碰到这种问题就很好解决了，通过终端找到npm install 的全局路径，chmod -R 777 获取提示的那个文件夹的权限就可以

windows的用户就按下面的方式来解决

如果解决不了就把WebStorm关掉，用终端输入对应的命令，不要用WebStorm里面的终端

（在对应的文件夹下按shift+鼠标右键，在此处打开命令窗口！！）

之前有时报这个，以为还真是权限不够，感觉有点奇怪，用管理员权限执行，有时还真有用，不过后面查了下，时缓存的问题，清理下缓存就行，不用管理员权限。

方法1、

需要删除npmrc文件。

强调：不是nodejs安装目录npm模块下的那个npmrc文件

而是在C:\Users\{账户}\下的.npmrc文件..

方法2、

或者直接用命令清理就行，控制台输入：

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: fsevents@1.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {“os”:”darwin”,”arch”:”any”} (current: {“os”:”win32”,”arch”:”x64”})

added 114 packages in 42.369s

成功了

Ran reactive-native init in command prompt as Administrator (on Windows OS), hoping works well with sudo reactive-native init on Mac OS
Ran npm cache clean command in Command prompt.
Disable your antivirus for time being.

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

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: fsevents@1.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {“os”:”darwin”,”arch”:”any”} (current: {“os”:”win32”,”arch”:”x64”})

added 114 packages in 42.369s

            </div>
                </div>