:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Перейти к файлу
Samuel Attard 5025c991ee
fix: pass the correct HostPort into the node inspector (#17380)
Fixes #17348
2019-03-18 09:19:33 -07:00
.circleci spec: initial spike of main-process based tests 2019-03-14 12:50:06 -07:00
.github
atom fix: pass the correct HostPort into the node inspector (#17380) 2019-03-18 09:19:33 -07:00
build
buildflags
chromium_src
components/pepper_flash
default_app chore: fix default_app showMessageBox (#17357) 2019-03-12 14:10:18 -07:00
docs refactor: implement clipboard APIs without the remote module (#17200) 2019-03-15 17:32:04 -07:00
docs-translations
lib fix: throw error when inserting menu items out-of-range (#17401) 2019-03-18 07:58:42 -07:00
manifests
native_mate
npm
patches chore: add description to accelerator.patch (#17346) 2019-03-13 10:11:07 +05:30
script fix: spec runner not parsing correctly 2019-03-15 10:57:12 -07:00
spec fix: pass the correct HostPort into the node inspector (#17380) 2019-03-18 09:19:33 -07:00
spec-main spec: fix fixtures path for second instance test 2019-03-15 12:29:25 -07:00
tools
typings spec: add new test runner for main-process based tests (#17325) 2019-03-17 14:49:00 -07:00
vendor
.clang-format
.dockerignore
.env.example
.eslintrc.json
.gitattributes
.gitignore
.gitmodules
.remarkrc
BUILD.gn feat: Add content script world isolation (#17032) 2019-03-11 16:27:57 -07:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
DEPS build: remove log from the spec runner 2019-03-14 12:50:06 -07:00
Dockerfile
Dockerfile.arm32v7
Dockerfile.arm64v8
ELECTRON_VERSION Bump v6.0.0-nightly.20190311 2019-03-11 10:56:01 -07:00
LICENSE
README.md
SECURITY.md
appveyor.yml
electron_paks.gni
electron_resources.grd
electron_strings.grdp
filenames.auto.gni
filenames.gni refactor: implement clipboard APIs without the remote module (#17200) 2019-03-15 17:32:04 -07:00
package-lock.json spec: initial spike of main-process based tests 2019-03-14 12:50:06 -07:00
package.json spec: initial spike of main-process based tests 2019-03-14 12:50:06 -07:00
tsconfig.default_app.json
tsconfig.electron.json
tsconfig.json
tsconfig.spec.json spec: initial spike of main-process based tests 2019-03-14 12:50:06 -07:00
vsts-arm-test-steps.yml
vsts-arm32v7.yml
vsts-arm64v8.yml

README.md

Electron Logo

CircleCI Build Status AppVeyor Build Status Azure Pipelines 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.