e93c587b8e
This removes the .node-version file, it is a source of confusion and not incredibly useful. It doesn't actually indicate the version of node that Electron uses, it's like a development helper that sets the version of node you should be using locally when devving on Electron. Not many major tools use it so too remove confusion I think we should remove it |
||
|---|---|---|
| .circleci | ||
| .github | ||
| atom | ||
| brightray | ||
| chromium_src | ||
| default_app | ||
| docs | ||
| docs-translations | ||
| lib | ||
| npm | ||
| script | ||
| spec | ||
| tools | ||
| vendor | ||
| .clang-format | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .remarkrc | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| common.gypi | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Dockerfile.arm64 | ||
| Dockerfile.arm64v8 | ||
| Dockerfile.armv7 | ||
| Dockerfile.circleci | ||
| electron.gyp | ||
| features.gypi | ||
| filenames.gypi | ||
| Jenkinsfile | ||
| Jenkinsfile.arm64 | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| toolchain.gypi | ||
📝 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 as Electron does not follow semantic
versioning. 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
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
- electronjs.org/docs - all of Electron's documentation
- electron/electron-quick-start - a very basic starter Electron app
- electronjs.org/community#boilerplates - sample starter apps created by the community
- electron/simple-samples - small applications with ideas for taking them further
- electron/electron-api-demos - an Electron app that teaches you how to use Electron
- hokein/electron-sample-apps - small demo apps for the various Electron APIs
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
You can ask questions and interact with the community in the following locations:
electroncategory on the Atom forums#atom-shellchannel on FreenodeAtomchannel on Slackelectron-ru(Russian)electron-br(Brazilian Portuguese)electron-kr(Korean)electron-jp(Japanese)electron-tr(Turkish)electron-id(Indonesia)electron-pl(Poland)
Check out awesome-electron for a community maintained list of useful example apps, tools and resources.
License
When using the Electron or other GitHub logos, be sure to follow the GitHub logo guidelines.