If you have a security concern, please see the security document.
If you're looking for programming help, for answers to questions, or to join in discussion with other developers who use Electron, you can interact with the community in these locations:
electroncategory on the Atom forums
#atom-shellchannel on Freenode
#electronchannel on Atom's Slack
If you'd like to contribute to Electron, see the contributing document.
awesome-electron is a community-maintained list of useful example apps, tools and resources.
The latest three stable major versions are supported by the Electron team. For example, if the latest release is 6.1.x, then the 5.0.x as well as the 4.2.x series are supported. We only support the latest minor release for each stable release series. This means that in the case of a security fix 6.1.x will receive the fix, but we will not release a new version of 6.0.x.
The latest stable release unilaterally receives all fixes from
and the version prior to that receives the vast majority of those fixes
as time and bandwidth warrants. The oldest supported release line will receive
only security fixes directly.
All supported release lines will accept external pull requests to backport
fixes previously merged to
master, though this may be on a case-by-case
basis for some older supported lines. All contested decisions around release
line backports will be resolved by the Releases Working Group as an agenda item at their weekly meeting the week the backport PR is raised.
When an API is changed or removed in a way that breaks existing functionality, the previous functionality will be supported for a minimum of two major versions when possible before being removed. For example, if a function takes three arguments, and that number is reduced to two in major version 10, the three-argument version would continue to work until, at minimum, major version 12. Past the minimum two-version threshold, we will attempt to support backwards compatibility beyond two versions until the maintainers feel the maintenance burden is too high to continue doing so.
When a release branch reaches the end of its support cycle, the series will be deprecated in NPM and a final end-of-support release will be made. This release will add a warning to inform that an unsupported version of Electron is in use.
These steps are to help app developers learn when a branch they're using becomes unsupported, but without being excessively intrusive to end users.
If an application has exceptional circumstances and needs to stay
on an unsupported series of Electron, developers can silence the
end-of-support warning by omitting the final release from the app's
devDependencies. For example, since the 1-6-x series
ended with an end-of-support 1.6.18 release, developers could choose
to stay in the 1-6-x series without warnings with
"electron": 1.6.0 - 1.6.17.
Following platforms are supported by Electron:
Only 64bit binaries are provided for macOS, and the minimum macOS version supported is macOS 10.10 (Yosemite).
Windows 7 and later are supported, older operating systems are not supported (and do not work).
amd64) binaries are provided for Windows.
Electron 6.0.8 and later add native support for Windows on Arm (
Running apps packaged with previous versions is possible using the ia32 binary.
amd64) binaries of Electron are built on
Ubuntu 12.04, the
armv7l binary is built against ARM v7 with hard-float ABI and
NEON for Debian Wheezy.
Until the release of Electron 2.0, Electron will also
continue to release the
armv7l binary with a simple
arm suffix. Both binaries
Whether the prebuilt binary can run on a distribution depends on whether the distribution includes the libraries that Electron is linked to on the building platform, so only Ubuntu 12.04 is guaranteed to work, but following platforms are also verified to be able to run the prebuilt binaries of Electron:
- Ubuntu 12.04 and newer
- Fedora 21
- Debian 8