ide-electron 在 Windows 10 x64(intel)平台打包报错

[fankangsong]

环境：

$ node -v && node-gyp -v && pnpm electron -v &&pnpm electron-builder --version
v16.19.0
v9.3.1

v18.3.4
23.3.3

MSBuilder 安装的是 2017 版本：

MSBuild /version
用于 .NET Framework 的 Microsoft (R) 生成引擎版本 15.9.21+g9802d43bc3
版权所有(C) Microsoft Corporation。保留所有权利。

15.9.21.664

具体的错误如下：

pnpm cross-env TARGET_ARCHES=x64 node build/pack.js
  • electron-builder  version=23.3.3 os=10.0.17134
  • author is missed in the package.json  appPackageFile=D:\web-ide\ide-electron\app\package.json
  • writing effective config  file=out\builder-effective-config.yaml
  • rebuilding native dependencies  dependencies=@parcel/watcher@2.0.5, node-pty@0.10.0, spdlog@0.11.1 platform=win32 arch=x64
  ⨯ cannot execute  cause=exit status 1
                    errorOut=npm ERR! code 1
    npm ERR! path D:\web-ide\ide-electron\app\node_modules\.pnpm\node-pty@0.10.0\node_modules\node-pty
    npm ERR! command failed
    npm ERR! command C:\Windows\system32\cmd.exe /d /s /c npm run build
    npm ERR! > node-pty@0.10.0 build
    npm ERR! > tsc -b ./src/tsconfig.json
    npm ERR!
    npm ERR! src/eventEmitter2.test.ts(8,1): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/eventEmitter2.test.ts(9,3): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/eventEmitter2.test.ts(19,3): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(49,1): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(50,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(51,5): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(59,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(60,5): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(70,5): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(82,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/terminal.test.ts(83,5): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(15,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(16,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(17,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(34,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(35,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(35,37): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(43,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(43,59): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(55,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(55,45): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(72,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(75,7): error TS2304: Cannot find name 'afterEach'.
    npm ERR! src/unixTerminal.test.ts(82,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(82,73): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(107,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(108,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(108,49): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(148,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(148,57): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(189,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(189,41): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/unixTerminal.test.ts(208,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/unixTerminal.test.ts(208,50): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsPtyAgent.test.ts(14,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(15,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(16,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(19,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(22,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(25,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(28,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(33,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(34,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(37,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(40,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(43,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(46,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(49,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(52,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(57,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(58,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(61,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(64,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(67,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(70,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(75,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(76,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(79,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(85,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(86,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsPtyAgent.test.ts(89,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(10,25): error TS2307: Cannot find module 'ps-list' or its corresponding type declarations.
    npm ERR! src/windowsTerminal.test.ts(26,34): error TS7006: Parameter 'ps' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(31,26): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(35,25): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(61,34): error TS7006: Parameter 'ps' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(63,33): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(63,57): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(69,21): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(69,54): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(71,22): error TS7006: Parameter 'p' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(84,11): error TS2794: Expected 1 arguments, but got 0. Did you forget to include 'void' in your type argument to 'Promise'?
    npm ERR! src/windowsTerminal.test.ts(92,3): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(93,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(94,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(94,46): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(100,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(100,58): error TS2503: Cannot find namespace 'Mocha'.
    npm ERR! src/windowsTerminal.test.ts(101,9): error TS2683: 'this' implicitly has type 'any' because it does not have a type annotation.
    npm ERR! src/windowsTerminal.test.ts(127,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(128,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(134,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(134,83): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(146,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(147,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(147,76): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(173,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(174,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(174,60): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(187,5): error TS2582: Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(188,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(188,52): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! src/windowsTerminal.test.ts(196,7): error TS2582: Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev
@types/mocha`.
    npm ERR! src/windowsTerminal.test.ts(196,56): error TS7006: Parameter 'done' implicitly has an 'any' type.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(265,87): error TS2694: Namespace '"fs"' has no exported member 'Dir'.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(268,17): error TS2694: Namespace '"fs"' has no exported member 'OpenDirOptions'.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(269,53): error TS2694: Namespace '"fs"' has no exported member 'Dir'.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(271,52): error TS2694: Namespace '"fs"' has no exported member 'OpenDirOptions'.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(271,80): error TS2694: Namespace '"fs"' has no exported member 'Dir'.
    npm ERR! ../../../../../../node_modules/.pnpm/@types+fs-extra@9.0.13/node_modules/@types/fs-extra/index.d.ts(382,52): error TS2694: Namespace '"fs"' has no exported member 'RmDirOptions'.

    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\fanks\AppData\Local\npm-cache\_logs\2023-02-28T07_37_43_246Z-debug-0.log

                    command=npm.cmd rebuild @parcel/watcher@2.0.5 node-pty@0.10.0 spdlog@0.11.1
                    workingDir=

D:\web-ide\ide-electron\node_modules\.pnpm\builder-util@23.3.3\node_modules\builder-util\src\util.ts:250
      reject(new ExecError(command, code, out, errorOut))
             ^
Error: D:\web-ide\ide-electron\node_modules\.pnpm\app-builder-bin@4.0.0\node_modules\app-builder-bin\win\x64\app-builder.exe process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
2
    at ChildProcess.<anonymous> (D:\web-ide\ide-electron\node_modules\.pnpm\builder-util@23.3.3\node_modules\builder-util\src\util.ts:250:14)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.cp.emit (D:\web-ide\ide-electron\node_modules\.pnpm\cross-spawn@7.0.3\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

[erha19]

@yantze 帮忙看下有没有遇到过类似问题？

[yantze]

看起来是编译类型报错，从 ide-electron 拉取最新的提交记录再试试

正常情况是下面这种，直接执行 pnpm run pack 就会打包

[fankangsong]

看起来是编译类型报错，从 ide-electron 拉取最新的提交记录再试试

正常情况是下面这种，直接执行 pnpm run pack 就会打包

在这个分支：

git log -1
commit 60c4ee7e778ffee3121a7e2ff2d0f3dc337157bb (HEAD -> main-cn, origin/main-cn)
Author: yutian.yz <yutian.yz@alibaba-inc.com>
Date:   Mon Mar 7 15:03:41 2022 +0800

    chore: add npm mirror config

执行：pnpm pack 后，out 目录是空的。

$ pnpm pack

> ide-electron@1.0.0 prepare D:\web-ide\ide-electron
> husky install

husky - Git hooks installed
ide-electron-1.0.0.tgz

fanks@kjzx2298153 MINGW64 /d/web-ide/ide-electron (main-cn)
$ ls out
builder-effective-config.yaml

[yantze]

刚更新一下了 main-cn 分支，git pull --rebase 拉取最新提交记录后再试试

[fankangsong]

@yantze 下午好，我找到了报错的来源：

electron-builder 执行打包时，应该会对如下几个包进行 node-gyp rebuild，我一一验证了下，这两个包编译会报错：

1. @opensumi/vscode-ripgrep
2. vscode-oniguruma

{
  "name": "opensumi-desktop",
  "version": "1.3.6",
  "main": "main/index.js",
  "description": "OpenSumi Desktop",
  "private": true,
  "dependencies": {
    "@opensumi/vscode-ripgrep": "^1.4.0",
    "node-pty": "0.10.0",
    "@parcel/watcher": "2.0.5",
    "spdlog": "0.11.1",
    "vscode-oniguruma": "^1.5.1"
  },
  "__npminstall_done": false
}

复现方法：

cd app && yarn
cd node_modules/@opensumi/vscode-ripgrep
node-gyp rebuild --openssl_fips=X --target=18.3.4 --arch=x64 --dist-url=https://electronjs.org/headers

以上操作都是在 Windows 10 平台操作的。

另外，我发现 pnpm 在 Windows 平台安装包，执行 pnpm rebuild-native -- --force-rebuild=true，scripts/rebuild-native.js 会有找不到 node_modules 目录的问题，使用 yarn 就没问题。

[yantze]

@yantze 下午好，我找到了报错的来源：

electron-builder 执行打包时，应该会对如下几个包进行 node-gyp rebuild，我一一验证了下，这两个包编译会报错：

1. @opensumi/vscode-ripgrep
2. vscode-oniguruma

{
  "name": "opensumi-desktop",
  "version": "1.3.6",
  "main": "main/index.js",
  "description": "OpenSumi Desktop",
  "private": true,
  "dependencies": {
    "@opensumi/vscode-ripgrep": "^1.4.0",
    "node-pty": "0.10.0",
    "@parcel/watcher": "2.0.5",
    "spdlog": "0.11.1",
    "vscode-oniguruma": "^1.5.1"
  },
  "__npminstall_done": false
}

复现方法：

cd app && yarn
cd node_modules/@opensumi/vscode-ripgrep
node-gyp rebuild --openssl_fips=X --target=18.3.4 --arch=x64 --dist-url=https://electronjs.org/headers

以上操作都是在 Windows 10 平台操作的。

另外，我发现 pnpm 在 Windows 平台安装包，执行 pnpm rebuild-native -- --force-rebuild=true，scripts/rebuild-native.js 会有找不到 node_modules 目录的问题，使用 yarn 就没问题。

这两个是不需要 rebuild 的，打包的时候会自动下载二进制。可以提供一下「报错的来源」 的截图看看

[fankangsong]

目前在 MacOS 上打包流程跑通了。

以下是在 Windows 执行打包后报错的截图：

[fankangsong]

现在解决的办法是：

1. 在 ./app 目录下手动 yarn 或者 npm 安装依赖；
2. build/pack.js 的 config 字段，新增如下，跳过依赖安装；

nodeGypRebuild: false,
npmRebuild: false,

不知道为什么 electron-builder 会无法安装依赖。

[MMhunter]

跳过 node-pty 安装依赖大概率会导致终端不可使用。。

实践中 node-pty 的 native module 构建确实非常纠结，特别是使用 electron 提供头文件的时候。

比较简单的方法是遵照 https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules 中的指示先手动在对应平台构建出 prebuild 。然后在 electron-builder 的时候跳过它自带的 node-gyp build 过程，把预先生成的 prebuild 拷贝进去。

[fankangsong]

跳过 node-pty 安装依赖大概率会导致终端不可使用。。

实践中 node-pty 的 native module 构建确实非常纠结，特别是使用 electron 提供头文件的时候。

比较简单的方法是遵照 https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules 中的指示先手动在对应平台构建出 prebuild 。然后在 electron-builder 的时候跳过它自带的 node-gyp build 过程，把预先生成的 prebuild 拷贝进去。

我试试，打完包node-pty 确认无法工作，terminal 启动报错，目前还没找到别的办法。

让我费劲的是 nodejs/node-gyp/MSbuilder 这三者直接的兼容关系，各种报错真的让人崩溃。

[fankangsong]

跳过 node-pty 安装依赖大概率会导致终端不可使用。。
实践中 node-pty 的 native module 构建确实非常纠结，特别是使用 electron 提供头文件的时候。
比较简单的方法是遵照 https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules 中的指示先手动在对应平台构建出 prebuild 。然后在 electron-builder 的时候跳过它自带的 node-gyp build 过程，把预先生成的 prebuild 拷贝进去。

我试试，打完包node-pty 确认无法工作，terminal 启动报错，目前还没找到别的办法。

让我费劲的是 nodejs/node-gyp/MSbuilder 这三者直接的兼容关系，各种报错真的让人崩溃。

@MMhunter 我理解 package.json 里 rebuild-native 执行的就是预编译，本地直接用 yarn start 其实终端是可以跑起来的，不明白为什么electron-builder 打包，node-gyp 就报错呢。

[yantze]

跳过 node-pty 安装依赖大概率会导致终端不可使用。。
实践中 node-pty 的 native module 构建确实非常纠结，特别是使用 electron 提供头文件的时候。
比较简单的方法是遵照 https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules 中的指示先手动在对应平台构建出 prebuild 。然后在 electron-builder 的时候跳过它自带的 node-gyp build 过程，把预先生成的 prebuild 拷贝进去。

我试试，打完包node-pty 确认无法工作，terminal 启动报错，目前还没找到别的办法。
让我费劲的是 nodejs/node-gyp/MSbuilder 这三者直接的兼容关系，各种报错真的让人崩溃。

@MMhunter 我理解 package.json 里 rebuild-native 执行的就是预编译，本地直接用 yarn start 其实终端是可以跑起来的，不明白为什么electron-builder 打包，node-gyp 就报错呢。

打包的时候，会重新对 build/package.json 的依赖进行安装和编译，可能会因为环境不同导致编译报错

[fankangsong]

打包的时候，会重新对 build/package.json 的依赖进行安装和编译，可能会因为环境不同导致编译报错

build/package.json 拷贝到 ./app/ 目录下，手动 yarn 其实是可以安装并编译成功的，但是使用 electron-builder 打包，就会报错。用 yarn 安装，和使用 electron-builder 进行安装依赖，不知道具体有什么差异。

[fankangsong]

最后升级到 MSBuild 2019，安装 vs install 的时候，把所有的安装项都勾选了，现在可以编译 exe 安装包了。