No description
Find a file
John Kleinschmidt e389fa75ea test: run all tests on arm linux platforms (#19318)
* test: run all tests on arm platforms

* Use Ubuntu 18.04 for arm64 CI
2019-07-19 16:15:47 -07:00
.circleci ci: do not use the MOCHA_FILE env variable (#19171) 2019-07-09 15:56:46 -05:00
.github docs: mention fiddle in bug report template (#19248) 2019-07-15 22:16:02 -07:00
build chore: update to latest TypeScript 3.5.2 (#19133) 2019-07-09 14:44:46 +03:00
buildflags
chromium_src chore: bump chromium to f1d9522c04ca8fa0a906f88ababe9 (master) (#18648) 2019-07-02 18:22:09 -07:00
components/pepper_flash
default_app fix: app.getAppPath() returning default-app path for files or directories without package.json (#18763) 2019-06-19 23:34:22 +02:00
docs feat: support isHighContrastColorScheme() on macOS (#19331) 2019-07-19 16:04:42 -07:00
docs-translations
lib chore: convert more files to TypeScript (#18820) 2019-07-17 10:23:52 -07:00
native_mate
npm build: ensure that we bundle the correct version of @types/node (#19102) 2019-07-03 16:36:59 -07:00
patches fix: bootstrap the node environment after we setup the InspectorAgent (#19317) 2019-07-18 16:54:23 -07:00
script test: run all tests on arm linux platforms (#19318) 2019-07-19 16:15:47 -07:00
shell feat: support isHighContrastColorScheme() on macOS (#19331) 2019-07-19 16:04:42 -07:00
spec chore: upgrade transitive lodash dependency (#19297) 2019-07-18 09:59:09 -07:00
spec-main test: robustify MenuItem label/accel tests (#19287) 2019-07-17 14:32:47 -07:00
tools chore: update to Node.js v12.4.0 (#18924) 2019-07-15 18:58:39 -07:00
typings chore: convert more files to TypeScript (#18820) 2019-07-17 10:23:52 -07:00
vendor
.clang-format
.dockerignore build: remove scripts in the tools dir that are unused (#18944) 2019-06-22 22:29:22 -07:00
.env.example
.eslintrc.json
.gitattributes
.gitignore
.gitmodules
.remarkrc
appveyor.yml fix: dump correct breakpad symbols on macOS (#19042) 2019-07-05 10:38:30 -07:00
BUILD.gn build: update symbol generation logic for all helpers (#19336) 2019-07-19 08:02:43 -07:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Update CONTRIBUTING.md 2019-06-19 15:52:11 -07:00
DEPS chore: upgrade node to 12.6.0 (#19312) 2019-07-17 14:22:27 -07:00
Dockerfile chore: bump chromium to f1d9522c04ca8fa0a906f88ababe9 (master) (#18648) 2019-07-02 18:22:09 -07:00
Dockerfile.arm32v7
Dockerfile.arm64v8 test: run all tests on arm linux platforms (#19318) 2019-07-19 16:15:47 -07:00
electron_paks.gni chore: bump chromium to 2a7aff41ce73adc0eeee67d364989 (master) (#18505) 2019-06-03 20:44:12 -07:00
electron_resources.grd
electron_strings.grdp chore: bump chromium to 2a7aff41ce73adc0eeee67d364989 (master) (#18505) 2019-06-03 20:44:12 -07:00
ELECTRON_VERSION Bump v7.0.0-nightly.20190719 2019-07-19 08:32:01 -07:00
filenames.auto.gni chore: convert more files to TypeScript (#18820) 2019-07-17 10:23:52 -07:00
filenames.gni chore: use dummy WebRequestNS when NetworkService is enabled (#19300) 2019-07-17 11:55:55 -07:00
LICENSE
package.json Bump v7.0.0-nightly.20190719 2019-07-19 08:32:01 -07:00
README.md docs: update badges (#18955) 2019-06-24 14:09:17 -07:00
SECURITY.md
tsconfig.default_app.json
tsconfig.electron.json
tsconfig.json chore: convert more files to TypeScript (#18820) 2019-07-17 10:23:52 -07:00
tsconfig.spec.json
vsts-arm-test-steps.yml test: run all tests on arm linux platforms (#19318) 2019-07-19 16:15:47 -07:00
vsts-arm32v7.yml chore: bump chromium to f1d9522c04ca8fa0a906f88ababe9 (master) (#18648) 2019-07-02 18:22:09 -07:00
vsts-arm64v8.yml test: run all tests on arm linux platforms (#19318) 2019-07-19 16:15:47 -07:00
yarn.lock chore: upgrade transitive lodash dependency (#19297) 2019-07-18 09:59:09 -07:00

Electron Logo

CircleCI Build Status AppVeyor Build Status devDependency Status

📝 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.

Contributing

If you are interested in reporting/fixing issues and contributing directly to the code base, please see CONTRIBUTING.md for more information on what we're looking for and how to get started.

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.