electron-forge npm run make native modules pah is error

#1339 # Issue Details

• Electron Forge Version: “@electron-forge/cli”: “^6.0.0-beta.39”,
• Electron Version: 8.1.1
• Operating System: MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)

Expected Behavior

i run cmd as npm run start, it work. but it can not work, when i run cmd as npm run make.
native modules can not find.
I expected it can work when i run npm run make.

Additional Information

i run cm as npm run make, it can make a package.dmg. I install it and open it. It happen error, some messages:

Uncaught Error: Cannot open /Users/qile/git/klive-teacher/teacher-package/src/lib/pdfmanager.node: Error: dlopen(/Users/qile/git/klive-teacher/teacher-package/src/lib/pdfmanager.node, 1): image not found

native modules path is error, it is not relative path, it is absolute path in my mac. I do not know how to resolve it.

my electron-forge conifg:

module.exports = {
  "packagerConfig": {
    "packageManager": "npm",
    "icon": "./make/xx",
    "asar": false,
    "overwrite": true,
    "extraResource": ["./src/lib/jar/", "./src/lib/jre/"]
  },
  "makers": [
    {
      "name": "@electron-forge/maker-squirrel",
      "config": {
        "name": "xx"
      }
    },
    {
      "name": "@electron-forge/maker-dmg",
      "platforms": [
        "darwin"
      ],
      "config": {
        "name": "xx",
        "icon": "./make/xx.ico"
      }
    },
    {
      "name": "@electron-forge/maker-deb",
      "config": {}
    },
    {
      "name": "@electron-forge/maker-rpm",
      "config": {}
    }
  ],
  "plugins": [
    [
      "@electron-forge/plugin-webpack",
      {
        "mainConfig": "./webpack.main.config.js",
        "renderer": {
          "config": "./webpack.renderer.config.js",
          "entryPoints": [
            {
              "html": "./src/index.html",
              "js": "./src/renderer.ts",
              "name": "main_window"
            }
          ]
        }
      }
    ]
  ]
};

I look forward to your reply

thanks

[this-spring]

I have the same issue as @this-spring, when creating a “child_process” inside electron-forge with webpack. The proposed node-loader removal @daijinru doesnt work in my case.

It works great in development with npm run start, but after building with npm run make and installng, the child process fails to load the required modules after installed.

Any ideas?

I resolve the problem by dynamically require. requireDynamically by absolutely path. like this:

const PdfAddon = requireDynamically(nodeUrl);
function requireDynamically(path)
{
    path = path.split('\\').join('/'); // Normalize windows slashes
    return eval(`require('${path}');`); // Ensure Webpack does not analyze the require statement
}

[cesarvarela]

The solution of using externals will break packaging because the modules won’t be copied to the native_modules folder 😕