No description
Find a file
John Kleinschmidt 1855144d26
Merge pull request #14663 from electron/add-fyi-job-for-chromium-tests
ci: add a FYI job to build Chromium test binaries
2018-09-18 10:14:58 -04:00
.circleci ci: add a FYI job to build Chromium test binaries 2018-09-18 14:01:20 +02: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 fix: quit properly in simpleFullScreen mode (#14620) 2018-09-16 22:22:09 -07:00
brightray chore: fix linting error on master (#14609) 2018-09-14 00:28:47 +10:00
build build: update electron patches (#14623) 2018-09-15 06:40:18 -05:00
chromium_src build: remove duplicate devtools sources (#14522) 2018-09-12 08:45:08 -05: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 feat: add will-redirect (#13866) 2018-09-16 01:42:43 +10:00
docs-translations update references to renamed i18n repo 2018-03-02 12:05:49 -08:00
lib chore: replace standard with eslint-config-standard and add custom rules (#14636) 2018-09-16 03:51:23 +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: update electron patches (#14623) 2018-09-15 06:40:18 -05:00
script chore: dont pass --stable through to bump-version.py (#14661) 2018-09-18 23:32:49 +10:00
spec chore: replace standard with eslint-config-standard and add custom rules (#14636) 2018-09-16 03:51:23 +10:00
tools chore: update to standard 12 2018-09-14 14:57:01 +10:00
vendor build: remove gyp build files (#14097) 2018-09-09 10:15:32 +09:00
.clang-format
.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 build: remove gyp build files (#14097) 2018-09-09 10:15:32 +09:00
.remarkrc
appveyor.yml ci: fix CI runs after 9e85bdb0 2018-09-14 17:50:03 +10:00
BUILD.gn fix: re-enable high-dpi support on windows (#14596) 2018-09-13 10:40:29 -05: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 will-redirect (#13866) 2018-09-16 01:42:43 +10:00
LICENSE prepare for merging to electron 2018-06-22 11:29:57 +10:00
package-lock.json chore: replace standard with eslint-config-standard and add custom rules (#14636) 2018-09-16 03:51:23 +10:00
package.json refactor: use one script to launch all linters (#14622) 2018-09-17 16:09:02 -05: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.