No description
Find a file
Cheng Zhao 54cbe5f749
feat: migrate protocol module to NetworkService (Part 9) (#18374)
* Compare final data instead of url

The behavior of did-finish-load and getURL has changed for redirects when
using NetworkService, so the test fails for NetworkService.

Comparing the finally received data makes the test more reliable.

* Implement intercept APIs

* Setting mimeType should set "content-type" header

* Passing no argument should not throw JS error

* Don't access api namespace in ProxyingURLLoaderFactory

* No need to create AtomURLLoaderFactory every time

* No use of weak factory
2019-05-24 11:28:00 +09:00
.circleci build: fix linux release builds on CircleCI (#18201) 2019-05-08 07:27:03 -07:00
.github chore: remove extra colon in Issue Details (#18359) 2019-05-21 15:45:03 +09:00
atom feat: migrate protocol module to NetworkService (Part 9) (#18374) 2019-05-24 11:28:00 +09:00
build build: ensure consistent lock files across multiple machines (#17955) 2019-04-30 13:59:47 -07:00
buildflags fix: port OSR code to new viz compositor codepath (#17538) 2019-04-17 14:10:04 -07:00
chromium_src GetNetCaptureModeFromCommandLine moved to net 2019-05-21 12:11:15 -07:00
components/pepper_flash chore: fix linking errors on Windows 2019-02-14 23:59:26 +05:30
default_app fix: correctly parse default_app path on windows (#18086) 2019-05-01 13:00:09 -07:00
docs refactor: netLog directly uses network service (#18289) 2019-05-23 15:31:38 -07:00
docs-translations
lib refactor: netLog directly uses network service (#18289) 2019-05-23 15:31:38 -07:00
native_mate docs: replace the atom.io headers URL with electronjs.org (#18328) 2019-05-21 16:17:07 +09:00
npm feat: add env variable to skip binary download on npm install (#17627) 2019-05-03 10:17:15 -07:00
patches roll patches 2019-05-23 10:39:06 -07:00
script build: move Windows release builds to AppVeyor cloud (#18337) 2019-05-23 16:54:34 -04:00
spec feat: migrate protocol module to NetworkService (Part 9) (#18374) 2019-05-24 11:28:00 +09:00
spec-main refactor: netLog directly uses network service (#18289) 2019-05-23 15:31:38 -07:00
tools docs: replace the atom.io headers URL with electronjs.org (#18328) 2019-05-21 16:17:07 +09:00
typings refactor: netLog directly uses network service (#18289) 2019-05-23 15:31:38 -07:00
vendor chore: temporarily use submodule and gn DEPS for requests/boto 2018-10-06 22:07:10 +13:00
.clang-format
.dockerignore ci: migrate libcc's Dockerfile to electron and update it (#14786) 2018-09-25 15:30:22 -04:00
.env.example build: move Windows release builds to AppVeyor cloud (#18337) 2019-05-23 16:54:34 -04:00
.eslintrc.json build: ensure consistent lock files across multiple machines (#17955) 2019-04-30 13:59:47 -07:00
.gitattributes chore: force patches to be checked out with LF line endings (#14789) 2018-09-26 02:04:32 +12:00
.gitignore build: ensure consistent lock files across multiple machines (#17955) 2019-04-30 13:59:47 -07:00
.gitmodules chore: temporarily use submodule and gn DEPS for requests/boto 2018-10-06 22:07:10 +13:00
.remarkrc
appveyor.yml build: notify MC of failures to allow easy reruns (#17981) 2019-04-26 12:35:43 -07:00
BUILD.gn v8/snapshot_toolchain.gni moved 2019-05-22 11:45:48 -07: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 chore: bump chromium in DEPS to 6a008993a2e54af93edd956a53c786668bc0e253 2019-05-23 06:00:22 -07:00
Dockerfile ci: migrate libcc's Dockerfile to electron and update it (#14786) 2018-09-25 15:30:22 -04:00
Dockerfile.arm32v7 ci: use ubuntu 18.04 for arm testing (#14988) 2018-10-05 09:29:32 -05:00
Dockerfile.arm64v8 ci: Trigger an arm test on VSTS after CircleCI build (#14898) 2018-10-04 12:01:16 -04:00
electron_paks.gni feat: Upgrade to Chromium 71.0.3578.98 (#15966) 2019-01-11 17:00:43 -08:00
electron_resources.grd chore: use c++ manifests instead of json 2019-02-14 23:59:26 +05:30
electron_strings.grdp refactor: printing implementation (#15143) 2018-11-09 14:42:34 +11:00
ELECTRON_VERSION Bump v7.0.0-nightly.20190523 2019-05-23 14:06:05 -07:00
filenames.auto.gni chore: remove leftover docs/api/structures/memory-info.md (#18421) 2019-05-23 15:25:52 -04:00
filenames.gni chore: bump chromium to 54af93edd956a53c786668bc0e253 (master) 2019-05-23 13:35:41 -07:00
LICENSE fix: update license year (#16287) 2019-01-05 12:53:20 -08:00
package.json Bump v7.0.0-nightly.20190523 2019-05-23 14:06:05 -07:00
README.md docs: add information about contributing (#17961) 2019-04-26 08:12:21 -07:00
SECURITY.md Change Contact Emails (#12278) 2018-03-15 04:37:40 +09:00
tsconfig.default_app.json chore: fix ts config to not complain about extraneous files (#16790) 2019-02-06 15:46:10 -08:00
tsconfig.electron.json chore: fix ts config to not complain about extraneous files (#16790) 2019-02-06 15:46:10 -08:00
tsconfig.json build: Update TypeScript, use @typescript-eslint (#17251) 2019-03-07 12:56:02 -08:00
tsconfig.spec.json spec: initial spike of main-process based tests 2019-03-14 12:50:06 -07:00
vsts-arm-test-steps.yml build: remove native mksnapshot for arm/arm64 (#17561) 2019-03-28 11:05:43 -04:00
vsts-arm32v7.yml ci: use ubuntu 18.04 for arm testing (#14988) 2018-10-05 09:29:32 -05:00
vsts-arm64v8.yml build: make torque patch more specific for native arm builds (#16992) 2019-02-18 10:02:50 +00:00
yarn.lock refactor: update husky ver 2.2.0 (#18300) 2019-05-22 14:03:06 -07:00

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.

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.