After upgrading GitHub Copilot CLI to `v1.0.46`, the CLI is no longer usable in my environment.
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
描述
### Describe the bug
It starts, prints the normal startup banner, but then immediately reports:
✗ Failed to start MCP Servers: Error: Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
### Affected version
GitHub Copilot CLI 1.0.46.
### Steps to reproduce the behavior
Version
GitHub Copilot CLI: 1.0.46
Previous version that worked: older versions / JS entry path still works in my environment
Installed globally with npm
Environment
OS: Linux
Architecture: x64
Node: v24.14.0
npm: installed globally with Node 24
glibc on system is relatively old
### Expected behavior
✗ Failed to start MCP Servers: Error: Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
### Additional context
_No response_
貢獻指南
研究方向
No source files or tests are named. Start by reproducing the global npm installation on Linux x64 with Node v24.14.0 and an older glibc, then compare the failing CLI path with the JS entry path that still works. Done means version 1.0.46 starts without the native-binding error and successfully starts its MCP servers.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- node.js
- 領域
- cli
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 冷清
- 描述清晰度
- 需要釐清
- 新手友好度
- 42/100