electron-packager | Electron app with OS-specific bundles ( .app , .exe , etc | Runtime Evironment library

SOLVED BY @chilkat Software by upgrading the current version of chilkat/ck-electron16-win64  and win32

Actually this is a bug, has been fixed 5 hours ago (Mar 14, 2022, 9:55 PM GMT)

GLOBAL_AGENT.HTTP_PROXY configuration value: URL protocol must be http

Just do:

We using electron-builder for packaging electron app on Windows&MacOS(x86_x64/arm etc.), and you can try it.

add some config in package.json, like this:

electron-packager's prune option removes any packages from the final bundle that are listed in the devDependencies section.

Since axios is listed there, it is removed from the bundle.

You should put it into the dependencies section and rebuild the bundle.

Use __dirname instead of .

. refers to the current working directory (cwd), which is the directory in which the node process was started.

For an unpackaged app, this is usually the root folder of your project, producing the expected results. For a packaged app, the cwd will likely be where the Electron executable is stored. The app's contents (what was previously the root folder) are put inside resources/app or resources/app.asar relative to the executable.

The way to unify the packaged and unpackaged scenarios is to use __dirname, which contains the directory of the currently running Node script. This way, it will be the same as using . in an unpackaged app, but will return the path with resources/app in the packaged scenario, as that is then the location of the currently running Node script.

This is why you'll often see people using something like `file://${__dirname}/assets/index.html` to address files in Electron.

If you use require('./file.js'), the path is evaluated relative to the location of the calling script and will work as if you had used __dirname.

Edit: Similar to the electron-builder solution I listed below, I searched the electron-packager doc and found a similar option for extra files, instead of "files" you will use "extraResource", check it out in the docs.

Original answer:

If you are using webpack to bundle your app before packaging, see if you can include it in your Javascript file and have a file loader in your webpack explained here(blog site), here (Stack overflow), and of course here (webpack official) . Be sure to install File-loader!

I prefer to use Electron builder for packaging apps, if you were to switch, you could include the file into your packaged app as follows:

List the audio file in your JSON settings (package.json) to be included in your packager e.g.:

I think your problem is the --asar option.

Because you have this option turned on electron-packager will package your source code into an app.asar file including your data folder.

Because your data folder has now been compressed with all your other source code into this app.asar file your code can no longer access it.

Solution 1:

• Take out: --asar

Solution 2:

• Add this option: --extra-resource=\"./data\"
• This'll tell electron-packager not to include ./data in the app.asar.

Read more about --asar

Read more about --extra-resource

Also see this StackOverflow question

I had similar issue, so I put icon in root project. change build script into something like this. It solved the problem.

calculator.png is in root project.

Packaging apps always messes with the file paths.
Just use relative file paths.