1. 为什么electron-builder打包总是失败第一次用electron-builder打包时我盯着满屏红色报错信息差点崩溃。后来才发现这些问题其实都有固定套路。electron-builder打包失败主要集中在三个环节环境配置占45%、网络问题占30%和配置错误占25%。最让人头疼的是错误提示往往语焉不详比如简单的Error: Exit code: 1就能让你debug一整天。我遇到最多的情况是卡在下载electron二进制包阶段。由于默认从GitHub下载国内网络环境经常出现连接超时或下载中断。有次我在公司打包进度条卡在62%整整半小时最后报错RequestError: read ECONNRESET。后来发现用淘宝镜像源能解决90%的下载问题具体操作是在项目根目录创建.npmrc文件加入electron_mirrorhttps://npm.taobao.org/mirrors/electron/另一个高频错误是Cant find required electron package。这通常发生在全局安装和项目本地安装版本不一致时。建议用npx确保使用项目本地安装的electron-builder版本npx electron-builder --mac --x642. 网络问题导致的打包失败解决方案2.1 手动下载electron二进制包当看到类似downloading electron-vxx.xx.x-darwin-x64.zip卡住时可以手动操作从报错信息复制下载URL如https://github.com/electron/electron/releases/download/v13.1.7/electron-v13.1.7-darwin-x64.zip用下载工具获取文件根据系统类型放到缓存目录macOS: ~/Library/Caches/electron/Windows: C:\Users[用户名]\AppData\Local\electron\Cache\Linux: ~/.cache/electron/实测发现有时需要先创建版本号子目录。比如electron-v13.1.7-darwin-x64.zip应该放在~/Library/Caches/electron/v13.1.7/目录下。2.2 配置国内镜像源除了淘宝镜像还有几种配置方式方法一修改npm配置npm config set electron_mirror https://cdn.npmmirror.com/binaries/electron/ npm config set electron_builder_binaries_mirror https://npmmirror.com/mirrors/electron-builder-binaries/方法二项目内.yarnrc配置electron_mirror https://cdn.npmmirror.com/binaries/electron/ electron_builder_binaries_mirror https://npmmirror.com/mirrors/electron-builder-binaries/方法三环境变量设置适合CI环境export ELECTRON_MIRRORhttps://cdn.npmmirror.com/binaries/electron/3. 环境配置常见陷阱3.1 系统架构不匹配在M1芯片Mac上打包x86应用时可能遇到Unsupported architecture错误。解决方案是安装Rosetta 2softwareupdate --install-rosetta通过arch指定架构arch -x86_64 npx electron-builder --mac --x643.2 证书签名问题macOS打包时报Apple Developer ID Application Certificate not found需要钥匙串访问中确认有开发者证书在package.json中添加mac: { hardenedRuntime: true, gatekeeperAssess: false, entitlements: entitlements.plist, entitlementsInherit: entitlements.plist }创建entitlements.plist文件?xml version1.0 encodingUTF-8? !DOCTYPE plist PUBLIC -//Apple//DTD PLIST 1.0//EN http://www.apple.com/DTDs/PropertyList-1.0.dtd plist version1.0 dict keycom.apple.security.cs.allow-jit/key true/ keycom.apple.security.cs.allow-unsigned-executable-memory/key true/ keycom.apple.security.cs.debugger/key true/ /dict /plist4. 配置文件中的隐藏坑4.1 asar打包异常启用asar加密后可能出现ENOENT: no such file or directory错误解决方法排查路径引用问题// 错误写法 const data require(./data.json) // 正确写法 const path require(path) const data require(path.join(__dirname, data.json))排除特定文件build: { asar: true, asarUnpack: [**/static/*, *.node] }4.2 资源文件丢失图片等静态资源经常在打包后消失正确的配置姿势build: { files: [ dist/**/*, node_modules/**/*, assets/**/*, !node_modules/.cache/**/* ], extraResources: [ { from: resources/${os}, to: resources, filter: [**/*] } ] }有个容易忽略的细节electron-builder默认只会打包files指定的文件node_modules里的devDependencies会被自动排除。如果需要打包dev依赖要显式声明build: { includeDevDependencies: true }5. 平台特定问题排查5.1 Windows系统常见错误错误一NSIS编译失败报错Error: Exit code: 1可能是NSIS版本问题解决方案安装最新NSIShttps://nsis.sourceforge.io/Download指定NSIS路径win: { target: nsis, nsis: { installerPath: C:/Program Files (x86)/NSIS/makensis.exe } }错误二图标格式无效Windows要求图标是.ico格式且包含多种尺寸推荐使用icoconvert.com生成符合要求的文件。5.2 Linux打包注意事项需要安装fakerootsudo apt-get install fakeroot指定deb依赖项linux: { target: [deb], depends: [ libgtk-3-0, libnotify4, libnss3 ] }6. 调试技巧与高级方案6.1 启用详细日志在命令后添加参数获取详细日志electron-builder --mac --x64 --debug更彻底的调试方式是设置环境变量export DEBUGelectron-builder,electron-builder:*6.2 自定义打包流程对于复杂项目可以编写afterPack脚本build: { afterPack: ./scripts/afterPack.js }示例脚本内容module.exports async (context) { const fs require(fs-extra) await fs.copy(custom/config.json, ${context.appOutDir}/resources/config.json) }6.3 使用docker打包对于需要多平台打包的情况推荐官方electronuserland/builder镜像FROM electronuserland/builder:wine COPY . /project RUN cd /project npm run build:linux npm run build:win最后提醒一个血泪教训永远在CI流程中锁定electron-builder版本我在团队协作中遇到过因为版本差异导致的构建不一致问题。推荐在package.json中精确指定devDependencies: { electron-builder: 24.4.0 }