@electron/packager
Advanced tools
Customize and package your Electron app with OS-specific bundles (.app, .exe, etc.) via JS or CLI
Package your Electron app into OS-specific bundles (.app, .exe, etc.) via JavaScript or the command line.
Supported Platforms | Installation | Usage | Contributing | Support | Related Apps/Libraries | FAQ | Release Notes
Electron Packager is a command line tool and Node.js library that bundles Electron-based application source code with a renamed Electron executable and supporting files into folders ready for distribution.
For creating distributables like installers and Linux packages, consider using either Electron Forge (which uses Electron Packager internally), or one of the related Electron tools, which utilizes Electron Packager-created folders as a basis.
Note that packaged Electron applications can be relatively large. A zipped, minimal Electron
application is approximately the same size as the zipped prebuilt binary for a given target
platform, target arch, and Electron version
(files named electron-v${version}-${platform}-${arch}.zip).
Electron Packager is known to run on the following host platforms:
It generates executables/bundles for the following target platforms:
win32, for x86, x86_64, and arm64 architectures)darwin) / Mac App Store (also known as mas)* (for x86_64, arm64, and universal architectures)* *Note for macOS / Mac App Store target bundles: the .app bundle can only be signed when building on a host macOS platform.*
This module requires Node.js 22.12.0 or higher to run.
npm install --save-dev @electron/packager
It is not recommended to install @electron/packager globally.
JavaScript API usage can be found in the API documentation.
Running Electron Packager from the command line has this basic form:
npx @electron/packager <sourcedir> <appname> --platform=<platform> --arch=<arch> [optional flags...]
This will:
<out>/<appname>-<platform>-<arch> (this can be customized via an optional flag)--platform and --arch can be omitted, in two cases:
--all instead, bundles for all valid combinations of target
platforms/architectures will be created.For an overview of the other optional flags, run electron-packager --help or see
usage.txt. For
detailed descriptions, see the API documentation.
For flags that are structured as objects, you can pass each option as via dot notation as such:
npx @electron/packager --flag.foo="bar"
# will pass in { flag: { foo: "bar"} } as an option to the Electron Packager API
If appname is omitted, this will use the name specified by "productName" or "name" in the nearest package.json.
Characters in the Electron app name which are not allowed in all target platforms' filenames
(e.g., /), will be replaced by hyphens (-).
You should be able to launch the app on the platform you built for. If not, check your settings and try again.
Be careful not to include node_modules you don't want into your final app. If you put them in
the devDependencies section of package.json, by default none of the modules related to those
dependencies will be copied in the app bundles. (This behavior can be turned off with the
prune: false API option or --no-prune CLI flag.) In addition, folders like .git and
node_modules/.bin will be ignored by default. You can use --ignore to ignore files and folders
via a regular expression (not a glob pattern).
Examples include --ignore=\.gitignore or --ignore="\.git(ignore|modules)".
Let's assume that you have made an app based on the minimal-repro repository on an Apple Silicon macOS device with the following file structure:
foobar
├── package.json
├── index.html
├── […other files, like the app's LICENSE…]
└── script.js
…and that the following is true:
@electron/packager is installed locallyproductName in package.json has been set to Foo Barelectron module is in the devDependencies section of package.json, and set to the exact version of 38.3.0.npm install for the Foo Bar app has been run at least onceWhen one runs the following command for the first time in the foobar directory:
npx @electron/packager .
@electron/packager will do the following:
sourcedirappname from the productName in package.jsonappVersion from the version in package.jsonplatform and arch from the host, in this example, darwin platform and arm64 arch.~/.electron)Foo Bar.appFoo Bar.app in foobar/Foo Bar-darwin-arm64/ (since an out directory was not specified, it used the current working directory)The file structure now looks like:
foobar
├── Foo Bar-darwin-x64
│ ├── Foo Bar.app
│ │ └── […Mac app contents…]
│ ├── LICENSE [the Electron license]
│ └── version
├── […other application bundles, like "Foo Bar-win32-x64" (sans quotes)…]
├── package.json
├── index.html
├── […other files, like the app's LICENSE…]
└── script.js
The Foo Bar.app folder generated can be executed by a system running macOS, which will start the packaged Electron app.
This is also true of the Windows x64 build on a Windows device (via Foo Bar-win32-x64/Foo Bar.exe), and so on.
Windows:
macOS:
Linux:
These Node modules utilize Electron Packager API hooks:
electron-builder is a complete solution to package and build a ready-for-distribution Electron app. It offers more advanced features like auto-update support, code signing, and publishing to various platforms. Compared to @electron/packager, it provides a more comprehensive set of tools for managing the entire build and release process.
electron-forge is a tool that helps you create, build, and publish Electron applications. It provides a more integrated experience with templates and plugins, making it easier to get started with Electron development. While @electron/packager focuses on packaging, electron-forge offers a broader set of features for the entire app lifecycle.
FAQs
Customize and package your Electron app with OS-specific bundles (.app, .exe, etc.) via JS or CLI
The npm package @electron/packager receives a total of 1,083,420 weekly downloads. As such, @electron/packager popularity was classified as popular.
We found that @electron/packager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.