npm WARN addRemoteGit Error: Command failed

最新推荐文章于 2025-07-02 15:49:27 发布
最新推荐文章于 2025-07-02 15:49:27 发布
阅读量6k 收藏 4
点赞数
CC 4.0 BY-SA版权
分类专栏： JavaScript 文章标签： node git npm
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/holdlg/article/details/53391780
本文解决npm安装过程中出现的错误，主要是因为缓存目录中的_git-remotes导致的问题。提供了删除缓存目录的方法，并介绍了如何设置代理来避免安装过程中的中断。

npm install error

npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit  amcharts/ammap3 resetting remote C:\Users\holdlg\AppData\Roaming\npm-cache\_git-remotes\git-github-com-amcharts-ammap3-git-5b4c9c11 because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }
npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit     at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit     at emitOne (events.js:96:13)
npm WARN addRemoteGit     at Socket.emit (events.js:188:7)
npm WARN addRemoteGit     at Pipe._handle.close [as _onclose] (net.js:501:12)
npm WARN addRemoteGit  amcharts/amcharts3 resetting remote C:\Users\holdlg\AppData\Roaming\npm-cache\_git-remotes\git-github-com-amcharts-amcharts3-git-867ad69c because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit     at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit     at emitOne (events.js:96:13)
npm WARN addRemoteGit     at Socket.emit (events.js:188:7)
npm WARN addRemoteGit     at Pipe._handle.close [as _onclose] (net.js:501:12)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }

解决方法

是因为npm缓存目录去缓存了个 _git-remotes 目录
windows路径：C:\Users\youname\AppData\Roaming\npm-cache
删除_git-remotes 再继续npm install。

如果总是中断，可以尝试设置代理试试。
(自备的Shadownsock代理地址http://127.0.0.1:1080)
git config –global http.proxy http://127.0.0.1:1080
git config –global https.proxy https://127.0.0.1:1080
git config –global http.proxy ‘socks5://127.0.0.1:1080’
git config –global https.proxy ‘socks5://127.0.0.1:1080’
取消代理
git config –global –unset http.proxy
git config –global –unset https.proxy

解决报错：ERROR Error: command failed: npm install --loglevel error --legacy-peer-deps
快乐学习
08-02 4078
轻松解决创建vue项目的时候在最后一步的时候创建失败了，报出了错误代码：npm ERR! code EPERM npm ERR! syscall open npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal ERROR Error: command failed: npm install --loglevel error --legacy-peer-deps
在idea的terminal上运行 npm install报npm WARN locking errno: -4048
qq_30505421的博客
07-10 2676
npm WARN locking errno: -4048,npm WARN locking code: 'EPERM',npm WARN locking syscall: 'open', D:\Code\Project\2021-3-1\ruoyi-vue\ruoyi-ui>npm install npm WARN locking Error: EPERM: operation not permitted, open ‘D:\Environment\nodejs\node_cache_l
git install 出错 Error: Command failed: git clone --depth=1 -q -b fix/ie-cannot-input-korean git://git
HouYing
08-13 1万+
3577 verbose stack Error: Command failed: git clone --depth=1 -q -b fix/ie-cannot-input-korean git://github.com/sohee-lee7/Squire.git C:\Users\tupos\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-f3923a54 --config core.longpaths=true 3577 verbose stack .
Command failed: git -c core.longpaths=true config --get remote.origin.url
张晋悦的博客
02-17 5921
「Unable to Connect to GitHub.com For Cloning」 此处原因应该是因为网络无法透过git://方式将package download下来 Error: Command failed: git -c core.longpaths=true config --get remote.origin.url 清除缓存：npm cache clear 更...
在win10上用户git上传长文件名的问题解决
最新发布
宁波阿成的博客
07-02 469
在win10上用户git上传长文件名的问题解决
Remove untracked files, stash or commit any changes, and try again. error Command failed with exit c
qq_35457469的博客
11-05 549
今天遇到这么一个问题: 使用create-react-app react-demo (react-demo项目名)创建了react项目后，一切正常，但是 当我需要修改webpack 配置的时候，突然发现，没有配置文件!!! 找了好多资料发现 人家的都会有webpack.config.js或者config，但唯独我的没有，最后我才发现怎么样才能找回这个配置文件…… 当我们需要暴露文件来易于后期对配置...
解决npm install各种报错的6种方案 Error: Command failed: cmd.exe autoreconf -ivf以及gifsicle pre-build test fail
tangdou369098655的博客
04-24 1万+
解决npm install各种报错的6种方案 Error: Command failed: cmd.exe autoreconf -ivf以及gifsicle pre-build test failed以及其他报错
npm install 错误问题 gyp ERR! configure error gyp ERR! stack Error: Command failed: C:\Users\Zhan
01-07
刚开始使用vscode打开一个已写好的vue。 1.根据网上教程，下载并配置好...npm WARN deprecated core-js@1.2.7: core-js@ fsevents@1.2.4 install /Users/changwei/project/react-first/node_modules/fsevents > node in
Microsoft Windows [版本 6.1.7601] 版权所有 (c) 2009 Microsoft Corporation。保留所有权利。 D:\newjobfile\codefile\newfilecode1\vuetestfile>npm run dev > vuetestfile@0.0.0 dev > vite 'vite' 不是内部或外部命令，也不是可运行的程序 或批处理文件。 D:\newjobfile\codefile\newfilecode1\vuetestfile>npm install npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'execa@9.5.2', npm WARN EBADENGINE required: { node: '^18.19.0 || >=20.5.0' }, npm WARN EBADENGINE current: { node: 'v19.9.0', npm: '9.6.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'vite@6.2.2', npm WARN EBADENGINE required: { node: '^18.0.0 || ^20.0.0 || >=22.0.0' }, npm WARN EBADENGINE current: { node: 'v19.9.0', npm: '9.6.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@vitejs/plugin-vue@5.2.3', npm WARN EBADENGINE required: { node: '^18.0.0 || >=20.0.0' }, npm WARN EBADENGINE current: { node: 'v19.9.0', npm: '9.6.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'nanoid@5.1.5', npm WARN EBADENGINE required: { node: '^18 || >=20' }, npm WARN EBADENGINE current: { node: 'v19.9.0', npm: '9.6.3' } npm WARN EBADENGINE } npm ERR! code 1 npm ERR! path D:\newjobfile\codefile\newfilecode1\vuetestfile\node_modules\esbui ld npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node install.js npm ERR! node:internal/errors:867 npm ERR! const err = new Error(message); npm ERR! ^ npm ERR! npm ERR! Error: Command failed: D:\newjobfile\nodefile\node.exe D:\newjobfile\co defile\newfilecode1\vuetestfile\node_modules\esbuild\bin\esbuild --version npm ERR! Exception 0xc0000005 0x8 0x0 0x0 npm ERR! PC=0x0 npm ERR! npm ERR! runtime.asmstdcall(0x2a0700060009) npm ERR! runtime/sys_windows_amd64.s:76 +0x89 fp=0xdaf780 sp=0xdaf760 pc= 0xd8e69 npm ERR! rax 0x0 npm ERR! rbx 0xa3c780 npm ERR! rcx 0xa844a8 npm ERR! rdx 0x20 npm ERR! rdi 0x7fffffde000 npm ERR! rsi 0xdaf978 npm ERR! rbp 0xdaf8c0 npm ERR! rsp 0xdaf758 npm ERR! r8 0xa3c4a0 npm ERR! r9 0xa840ca npm ERR! r10 0xdba2e8 npm ERR! r11 0xc000004000 npm ERR! r12 0xdaf9c8 npm ERR! r13 0x0 npm ERR! r14 0xa3b660 npm ERR! r15 0x3 npm ERR! rip 0x0 npm ERR! rflags 0x10246 npm ERR! cs 0x33 npm ERR! fs 0x53 npm ERR! gs 0x2b npm ERR! node:child_process:924 npm ERR! throw err; npm ERR! ^ npm ERR! npm ERR! Error: Command failed: D:\newjobfile\codefile\newfilecode1\vuetestfile\ node_modules\@esbuild\win32-x64\esbuild.exe --version npm ERR! at checkExecSyncError (node:child_process:885:11) npm ERR! at Object.execFileSync (node:child_process:921:15) npm ERR! at Object.<anonymous> (D:\newjobfile\codefile\newfilecode1\vuetestf ile\node_modules\esbuild\bin\esbuild:221:28) npm ERR! at Module._compile (node:internal/modules/cjs/loader:1275:14) npm ERR! at Module._extensions..js (node:internal/modules/cjs/loader:1329:10 ) npm ERR! at Module.load (node:internal/modules/cjs/loader:1133:32) npm ERR! at Module._load (node:internal/modules/cjs/loader:972:12) npm ERR! at Function.executeUserEntryPoint [as runMain] (node:internal/modul es/run_main:83:12) npm ERR! at node:internal/main/run_main_module:23:47 { npm ERR! status: 2, npm ERR! signal: null, npm ERR! output: [ null, null, null ], npm ERR! pid: 7396, npm ERR! stdout: null, npm ERR! stderr: null npm ERR! } npm ERR! npm ERR! Node.js v19.9.0 npm ERR! npm ERR! at checkExecSyncError (node:child_process:885:11) npm ERR! at Object.execFileSync (node:child_process:921:15) npm ERR! at validateBinaryVersion (D:\newjobfile\codefile\newfilecode1\vuete stfile\node_modules\esbuild\install.js:101:28) npm ERR! A complete log of this run can be found in: D:\newjobfile\nodefile\node _cache\_logs\2025-03-20T00_55_22_540Z-debug-0.log D:\newjobfile\codefile\newfilecode1\vuetestfile>
03-21
好的，我现在需要帮用户解决他们在运行npm run dev时遇到的错误。首先，用户的环境是Windows 7，系统版本是6.1.7601，看起来比较旧了。他们运行的是Vue项目，使用Vite，但执行npm run dev时报错说'vite'不是可执行...
E:\IDEA_files\test\testvue01>npm install npm WARN locking Error: EPERM: operation not permitted, open 'E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock' npm WARN locking E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock failed [Error: EPERM: operation not permitted, open 'E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock'] { npm WARN locking errno: -4048, npm WARN locking code: 'EPERM', npm WARN locking syscall: 'open', npm WARN locking path: 'E:\\node.js\\node_cache\\_locks\\staging-e46407c84593f6b3.lock' npm WARN locking } npm ERR! code EPERM npm ERR! syscall open npm ERR! path E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock' npm ERR! [Error: EPERM: operation not permitted, open 'E:\node.js\node_cache\_locks\staging-e46407c84593f6b3.lock'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'E:\\node.js\\node_cache\\_locks\\staging-e46407c84593f6b3.lock' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator.
04-25
好的，我现在需要帮助用户解决在Windows上使用npm install时遇到的EPERM错误，特别是与权限问题和锁定文件相关的情况。首先，我需要回顾用户的问题和提供的引用内容。 用户提到之前安装cnpm时遇到了EPERM错误，错误...
C:\xtreme1-main\frontend\main>npm install npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup 'C:\\xtreme1-main\\frontend\\main\\node_modules\\cwebp-bin', npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\xtreme1-main\frontend\main\node_modules\cwebp-bin'] { npm WARN cleanup errno: -4082, npm WARN cleanup code: 'EBUSY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: 'C:\\xtreme1-main\\frontend\\main\\node_modules\\cwebp-bin' npm WARN cleanup } npm WARN cleanup ], npm WARN cleanup [ npm WARN cleanup 'C:\\xtreme1-main\\frontend\\main\\node_modules\\cwebp-bin', npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\xtreme1-main\frontend\main\node_modules\cwebp-bin'] { npm WARN cleanup errno: -4082, npm WARN cleanup code: 'EBUSY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: 'C:\\xtreme1-main\\frontend\\main\\node_modules\\cwebp-bin' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 1 npm ERR! path C:\xtreme1-main\frontend\main\node_modules\gifsicle npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node lib/install.js npm ERR! compiling from source npm ERR! unable to verify the first certificate npm ERR! gifsicle pre-build test failed npm ERR! Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "autoreconf -ivf" npm ERR! 'autoreconf' �����ڲ����ⲿ���Ҳ���ǿ����еij��� npm ERR! ���������ļ��� npm ERR! npm ERR! npm ERR! at C:\xtreme1-main\frontend\main\node_modules\bin-build\node_modules\execa\index.js:231:11 npm ERR! at processTicksAndRejections (node:internal/process/task_queues:96:5) npm ERR! at async Promise.all (index 0)
03-27
好的，我现在需要解决用户提到的两个问题：npm安装时的EBUSY错误和gifsicle预构建测试失败。首先，我得分别分析这两个问题的可能原因，然后找出解决方法。 关于EBUSY错误，通常这指的是文件或资源被占用，导致npm...
git pull失败
yuhui666666的博客
09-16 233
git 先提交，冲突后，pull失败可能是版本滞后，可以先merger一下
git pull 后报错问题
weixin_30478923的博客
09-05 117
下面的错误： 1 $ git pull 2 Password: 3 You asked me to pull without telling me which branch you 4 want to merge with, and 'branch.master.merge' in 5 your configuration file does not tell me...
git 操作常见错误及解决方式---(实战性总结)
GXing007的博客
12-11 5283
GitBash 配置到WebStorm中 File–>settings–>Tools–>Terminal 更改Shell Path中cmd.exe为sh.exe的路径 注意：这里的路径是sh.exe的路径不是gitbash.exe的路径 "C:\Program Files\Git\bin\sh.exe" --login -i 解决git pull/git push 每次都...
解决Git提交失败的问题：配置user.name和user.email
Clang’s Blog
04-30 1万+
在本文中，我们介绍了解决Git提交失败问题的一种常见原因，并提供了详细的解决办法。通过配置“user.name”和“user.email”，你可以确保在提交代码时Git能够正确地识别你的身份信息，顺利完成提交操作。
git用户名配置不显示user.name及user.email报错及解决
jinyeran的博客
12-28 1万+
解决方案：仔细核对输入格式 注意邮箱没有“”，name和email后有空格
error Command failed.报错问题解决（Linux下/Windows下）
热门推荐
weixin_46900108的博客
09-20 2万+
我们在运行vue脚本项目时很容易遇到这种问题，比如新机房电脑或者第一次运行某个项目时遇到error Command failed报错 解决这一报错的完美解决为 npm install chromedriver --chromedriver_cdnurl=http://cdn.npm.taobao.org/dist/chromedriver 运行这个，安装驱动即可以完美解决问题 注意这里，我们一定要通过淘宝镜像进行安装，否则会很慢。我们执行完这段命令后，在执行npm install 就不会出现因为错误而被
使用app-inspector查看元素，无法连接到手机，提示错误{ Error: Command failed ……forward tcp:9001 tcp:9001错误解决...
weixin_30462049的博客
12-07 622
在学习使用app-inspector查看元素时，碰到一个问题。在cmd窗口执行命令app-inspector --port 5678 -u 85EABNFSU53R --verbose ，连接不到手机，提示如下： { Error: Command failed: E:\app_auto_test\android SDK\android-sdk-windows\platfrm-tools\adb...
Git命令的使用记录及常见的错误解决方式
Mango先生的博客
12-13 1万+
Git在现在应该是使用得最多的版本管理工具了，本片博客将持续更新它的使用方法，以及在平时开发中遇到的问题及解决方法，至于它与SVN或者其它的工具有什么区别这里就不谈了，不是重点
评论 5
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值