node.js - 使用重新构建的Electron的Electron Packager脚本错误

Question

我正在使用使用sqlite3的Electron应用程序。由于我使用的是sqlite3，因此在命令之后使用“electron-rebuild”重建了项目:

electron-rebuild -f -w sqlite3 

然后，它可以成功工作。

完成项目后，我需要使用“Electron-Packager”制作一个包装。这就是为什么我借助互联网编写脚本('build.js')的原因。该脚本如下:

const packager = require('electron-packager');
const rebuild = require('electron-rebuild');

packager({
    buildPath: __dirname,
    electronVersion: '7.1.2',
    dir: '../output',
    overwrite: true,
    asar: true,
    platform: 'win32',
    arch: 'ia32',
    icon: '/src/img/icon.ico',
    prune: true,
    out: 'project-name',
    executableName: 'project-name',
    afterCopy: [(buildPath, electronVersion, platform, arch, callback) => {
        rebuild.rebuild({ buildPath, electronVersion, arch })
            .then(() => callback())
            .catch((error) => callback(error));
    }],
})

运行脚本后，出现错误，那就是:

(node:7712) UnhandledPromiseRejectionWarning: Error: Unable to find all properties in parent package.json files. Missing props: ["productName","name"], "version", "author"
    at C:\[[project-location]]\node_modules\get-package-info\lib\index.js:23:17
    at tryCatcher (C:\[[project-location]]\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\[[project-location]]\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\[[project-location]]\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\[[project-location]]\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\[[project-location]]\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\[[project-location]]\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\[[project-location]]\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\[[project-location]]\node_modules\bluebird\js\release\async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (C:\[[project-location]]\node_modules\bluebird\js\release\async.js:15:14)
    at processImmediate (internal/timers.js:439:21)
(node:7712) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7712) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

我正在使用的package.json是:

{
  "name": "project-name",
  "version": "1.0.0",
  "description": "",
  "main": "main.js",
  "scripts": {
    "start": "electron .",
    "rebuild": "electron-rebuild -f -w sqlite3 ",
    "package": "node build.js"
  },
  "productName": "project-name",
  "author": "Takiuddin Ahmed",
  "license": "MIT",
  "devDependencies": {
    "electron": "^7.1.2",
    "electron-packager": "^14.2.0",
    "electron-rebuild": "^1.9.0"
  },
  "dependencies": {
    "sqlite3": "^4.1.1"
  }
}

Answer 1

我通过重写'build.js'解决了这个问题。

我得到了 Electron 包装机的API Documentation，在那里我发现我的构建脚本中需要指定一些选项。在这些选项中，win32metadata.companyName，name和buildVersion是必需的，但默认情况下，值应从“package.json”设置。
package.json中的'win32metadata.companyName'默认为'作者'名称，'name'默认为'productName'，'buildVersion'默认为'version'。但是无论如何，程序无法从“package.json”获得这些选项。因此，我只在“build.js”中指定这些选项。它的工作原理。我最终的“build.js”脚本是:

const packager = require('electron-packager');
const rebuild = require('electron-rebuild');

packager({
    name: "project-name",
    buildPath: __dirname,
    electronVersion: '7.1.2',
    version: '1.0.1',
    buildVersion: '1.0.1',
    dir: '../output',
    overwrite: true,
    asar: true,
    platform: 'win32',
    arch: 'ia32',
    icon: '/src/img/icon.ico',
    prune: true,
    appVersion: "1.0.1",
    win32metadata: {
        CompanyName: "Takiuddin Ahmed"
    },
    afterCopy: [(buildPath, electronVersion, platform, arch, callback) => {
        rebuild({ buildPath, electronVersion, arch })
            .then(() => callback())
            .catch((error) => callback(error));
    }],
});