By default electron-builder downloads the entire electron version that is defined in the package management file (e.g.

Many projects use electron-builder to build and package the Javascript file and Electron binaries. Using electron-builder with system electron Make sure to adjust the path for all further commands that make use of the. Set HOME to a path inside the $srcdir so the build process does not place any files in your real HOME directory. The build system will download the prebuilt copy it requires, compile the native extensions, and package everything into a final distribution, but this can be pruned during the package() step as usual.Īlternatively, you can remove the electron dependency from package.json and set the correct environment variables before running npm:Įxport npm_config_target=$(tail /usr/lib/electron/version) Since npm/yarn will always build against a private prebuilt copy of electron, patch the electron dependency from package.json to reference the same version as the system electron dependency. Some electron applications have compiled native extensions which link to the electron runtime, and must be built using the correct electron version. Everything else is just a copy of the electron runtime and can be removed from the final package.īuilding compiled extensions against the system electron This document covers standards and guidelines on writing PKGBUILDs for Electron.Īrch Linux provides global electron and versioned electron* packages that can be used to run an electron application via a shellscript wrapper:Įxec electron /path/to/ appname/ appname/ directory, or alternatively a file bundle called appname.asar, can be found in a prebuilt electron application as the resources/app/ folder (or resources/app.asar). 32-bit – CLR – CMake – Cross – DKMS – Eclipse – Electron – Font – Free Pascal – GNOME – Go – Haskell – Java – KDE – Kernel – Lisp – Meson – MinGW – Node.js – Nonfree – OCaml – Perl – PHP – Python – R – Ruby – Rust – Shell – VCS – Web – Wine

Npm create electron app