Angular 15升级至16时遇esbuild相关npm错误求助

问题背景 #

升级Angular项目从15到16版本时，执行npm安装/升级命令触发esbuild相关错误，核心报错为：

Error: spawnSync C:\Users\WebContent\node_modules\@esbuild\win32-x64\esbuild.exe UNKNOWN

移除@angular-devkit/build-angular依赖后升级可正常完成，但该依赖是Angular构建必需项；已尝试删除node_modules目录和package-lock.json文件，问题仍未解决。当前项目package.json配置如下：

{
  "name": "web-content",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^16.2.8",
    "@angular/cdk": "^16.2.7",
    "@angular/common": "^16.2.8",
    "@angular/compiler": "^16.2.8",
    "@angular/core": "^16.2.8",
    "@angular/forms": "^16.2.8",
    "@angular/material": "^16.2.7",
    "@angular/platform-browser": "^16.2.8",
    "@angular/platform-browser-dynamic": "^16.2.8",
    "@angular/router": "^16.2.8",
    "core-js": "^2.4.1",
    "ng-chartjs": "^0.0.7",
    "rxjs": "^7.8.1",
    "tslib": "^2.6.2",
    "zone.js": "^0.13.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^16.2.5",
    "@angular/cli": "^16.2.5",
    "@angular/compiler-cli": "^16.2.8",
    "@angular/language-service": "^16.2.8",
    "@types/jasmine": "~3.6.0",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "^14.0.4",
    "codelyzer": "^6.0.0",
    "fs-monkey": "^1.0.4",
    "jasmine-core": "~3.8.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~3.2.0",
    "tslint": "~6.1.0",
    "typescript": "^4.9.3"
  }
}

解决步骤 #

1. 固定esbuild版本 #

Angular 16的@angular-devkit/build-angular依赖特定版本的esbuild，版本不兼容可能导致安装异常。在package.json的devDependencies中添加固定版本的esbuild：

"esbuild": "0.18.20"

然后执行清理和安装命令：

# Windows系统
rmdir /s /q node_modules && del package-lock.json
# macOS/Linux系统
rm -rf node_modules package-lock.json

npm install

2. 跳过esbuild二进制校验 #

esbuild安装时会校验二进制文件完整性，若网络或权限问题导致二进制损坏，可设置环境变量跳过校验：

• CMD（Windows）：

  set ESBUILD_SKIP_INSTALL=1
  npm install
  

• PowerShell（Windows）：

  $env:ESBUILD_SKIP_INSTALL=1
  npm install
  

此方法会让esbuild使用JavaScript版本，性能略有下降，但可解决安装问题。

3. 以管理员权限执行命令 #

UNKNOWN错误可能与文件权限有关，右键命令提示符或PowerShell，选择「以管理员身份运行」，再执行npm install。

4. 更换包管理器尝试 #

若npm仍存在问题，可换用pnpm或yarn：

• pnpm：

  npm install -g pnpm
  pnpm install
  

• yarn：

  npm install -g yarn
  yarn install
  

5. 清理npm缓存 #

缓存损坏也可能导致依赖安装异常：

npm cache clean --force
rm -rf node_modules package-lock.json # Windows对应命令见步骤1
npm install

内容的提问来源于stack exchange，提问作者juliastoelli