No description
Find a file
2018-09-20 22:37:56 +10:00
.circleci Merge pull request #14672 from electron/use-smaller-machines-on-linux-ci 2018-09-19 13:51:58 -04:00
.github chore: ask for specific info in bug templates (#14229) 2018-08-22 08:21:54 -07:00
.vsts refactor: use one script to launch all linters (#14622) 2018-09-17 16:09:02 -05:00
atom chore: turn off clang-format for ATOM_PRE_RELEASE_VERSION (#14711) 2018-09-20 16:55:07 +10:00
brightray chore: run clang-format 2018-09-19 17:18:10 +02:00
build build: with enable_extensions=false (#14657) 2018-09-18 11:04:54 -07:00
chromium_src chore: run clang-format 2018-09-19 17:18:10 +02:00
components/pepper_flash Rename buildflag_headers for consistency 2018-09-11 20:21:32 +02:00
default_app chore: update to standard 12 2018-09-14 14:57:01 +10:00
docs docs: type the promises in our docs (#14715) 2018-09-20 22:37:56 +10:00
docs-translations update references to renamed i18n repo 2018-03-02 12:05:49 -08:00
lib [RFC] perf: use an internal module resolver to improve require performance (#14633) 2018-09-20 13:43:26 +10:00
native_mate [wip] build: try building node with GN 2018-08-10 10:06:27 -07:00
npm chore: update to standard 12 2018-09-14 14:57:01 +10:00
patches build: with enable_extensions=false (#14657) 2018-09-18 11:04:54 -07:00
script fix: change subprocess.Popen calls to work on Linux too (#14689) 2018-09-20 16:57:21 +10:00
spec test: runas is not an optional dependency (#14704) 2018-09-19 15:59:37 -07:00
tools chore: update to standard 12 2018-09-14 14:57:01 +10:00
vendor chore: remove vendored depot_tools (#14676) 2018-09-19 09:37:38 -07:00
.clang-format Add clang-format config file. 2016-10-04 22:42:49 +02:00
.dockerignore Add testing for arm, arm64 and ia32 linux builds 2017-12-20 11:54:52 -05:00
.env.example clarify purpose of .env.example 2018-07-11 12:55:15 -07:00
.eslintrc chore: replace standard with eslint-config-standard and add custom rules (#14636) 2018-09-16 03:51:23 +10:00
.gitignore chore: replace standard with eslint-config-standard and add custom rules (#14636) 2018-09-16 03:51:23 +10:00
.gitmodules chore: remove vendored depot_tools (#14676) 2018-09-19 09:37:38 -07:00
.remarkrc add remark lint to ensure fenced codeblocks are formatted properly. 2017-11-20 14:05:47 +08:00
appveyor.yml ci: fix CI runs after 9e85bdb0 2018-09-14 17:50:03 +10:00
BUILD.gn [RFC] perf: use an internal module resolver to improve require performance (#14633) 2018-09-20 13:43:26 +10:00
CODE_OF_CONDUCT.md Change Contact Emails (#12278) 2018-03-15 04:37:40 +09:00
CONTRIBUTING.md add docs/development/README.md (#12373) 2018-03-20 15:36:48 -04:00
DEPS build: move libcc patches to electron repo (#14104) 2018-09-13 22:02:16 -07:00
Dockerfile Use Node.js 10 for CI builds 2018-06-19 11:49:45 +10:00
Dockerfile.arm64 Newer CI images (#12188) 2018-03-08 22:07:50 -05:00
Dockerfile.arm64v8 Update CI to use Node 8 2018-03-19 10:19:32 -04:00
Dockerfile.armv7 Update CI to use Node 8 2018-03-19 10:19:32 -04:00
Dockerfile.circleci Use Node.js 10 for CI builds 2018-06-19 11:49:45 +10:00
electron.gyp build: remove gyp build files (#14097) 2018-09-09 10:15:32 +09:00
electron_paks.gni build: remove duplicate devtools sources (#14522) 2018-09-12 08:45:08 -05:00
filenames.gni feat: add process.takeHeapSnapshot() / webContents.takeHeapSnapshot() (#14456) 2018-09-18 11:00:31 -07:00
LICENSE Update license year 2018-01-01 00:51:40 +01:00
package-lock.json docs: type the promises in our docs (#14715) 2018-09-20 22:37:56 +10:00
package.json docs: type the promises in our docs (#14715) 2018-09-20 22:37:56 +10:00
README.md docs: Add Electron Fiddle to the readme (#14396) 2018-08-31 22:56:55 -07:00
SECURITY.md Change Contact Emails (#12278) 2018-03-15 04:37:40 +09:00
vsts.yml ci: Move Mac builds to Azure Devops (VSTS) (#14588) 2018-09-14 11:56:16 -07:00

Electron Logo

CircleCI Build Status AppVeyor Build Status devDependency Status Join the Electron Community on Slack

📝 Available Translations: 🇨🇳 🇹🇼 🇧🇷 🇪🇸 🇰🇷 🇯🇵 🇷🇺 🇫🇷 🇹🇭 🇳🇱 🇹🇷 🇮🇩 🇺🇦 🇨🇿 🇮🇹. View these docs in other languages at electron/i18n.

The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on Node.js and Chromium and is used by the Atom editor and many other apps.

Follow @ElectronJS on Twitter for important announcements.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to coc@electronjs.org.

Installation

To install prebuilt Electron binaries, use npm. The preferred method is to install Electron as a development dependency in your app:

npm install electron --save-dev [--save-exact]

The --save-exact flag is recommended for Electron prior to version 2, as it does not follow semantic versioning. As of version 2.0.0, Electron follows semver, so you don't need --save-exact flag. For info on how to manage Electron versions in your apps, see Electron versioning.

For more installation options and troubleshooting tips, see installation.

Quick start & Electron Fiddle

Use Electron Fiddle to build, run, and package small Electron experiments, to see code examples for all of Electron's APIs, and to try out different versions of Electron. It's designed to make the start of your journey with Electron easier.

Alternatively, clone and run the electron/electron-quick-start repository to see a minimal Electron app in action:

git clone https://github.com/electron/electron-quick-start
cd electron-quick-start
npm install
npm start

Resources for learning Electron

Programmatic usage

Most people use Electron from the command line, but if you require electron inside your Node app (not your Electron app) it will return the file path to the binary. Use this to spawn Electron from Node scripts:

const electron = require('electron')
const proc = require('child_process')

// will print something similar to /Users/maf/.../Electron
console.log(electron)

// spawn Electron
const child = proc.spawn(electron)

Mirrors

Documentation Translations

Find documentation translations in electron/i18n.

Community

Info on reporting bugs, getting help, finding third-party tools and sample apps, and more can be found in the support document.

License

MIT

When using the Electron or other GitHub logos, be sure to follow the GitHub logo guidelines.