98e91ca555
* fix: pre-create thinlto-cache dir on Windows to avoid bindflt race Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com> * fix: discover ThinLTO cache path from GN instead of hardcoding Addresses review feedback from @deepak1556: the hardcoded `out\Default\thinlto-cache` path goes out of sync if upstream changes `cache_dir` in Chromium's build/config/compiler/BUILD.gn. Read the `/lldltocache:` flag from `gn desc` on a linked target (`//electron:electron_app`) and pre-create whatever path GN actually configured. Skips the pre-create entirely when ThinLTO is disabled (non-official builds), which is the correct no-op. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: run gn gen before discovering ThinLTO cache path Previous attempt failed on Windows CI for two reasons: 1. `e init` does not run `gn gen` — out/Default is still unpopulated when the build step starts, so `gn desc` had nothing to introspect. 2. `e` writes informational lines to stderr (e.g. "INFO Auto-updates disabled"), which GitHub Actions' default $ErrorActionPreference = 'Stop' turned into a terminating NativeCommandError before e build could run. Run `gn gen` explicitly here so `gn desc` can report the effective `/lldltocache:` path, and shell each `e` invocation through cmd.exe so its informational stderr stays out of PowerShell's error stream. `e build` re-uses the same generated build dir so gn gen is paid once. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: revert to hardcoded thinlto-cache path, document the coupling Dynamic discovery via `gn desc` required `gn gen` to run beforehand, and `gn gen` can't run before `e build` on Windows CI — gn.exe isn't installed in `src/third_party/gn/` or `src/buildtools/win/gn/` until a Chromium gclient hook that the current CI workflow doesn't trigger. `e build` works because the restored src cache lets it skip the gen step; any attempt to force `gn gen` earlier fails with exit 2. Go back to pre-creating the path the upstream default currently resolves to, and leave a comment explaining the coupling so a future upstream relocation fails loudly (via the original LLVM error) rather than silently. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude <svc-devxp-claude@slack-corp.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
📝 Available Translations: 🇨🇳 🇧🇷 🇪🇸 🇯🇵 🇷🇺 🇫🇷 🇺🇸 🇩🇪. View these docs in other languages on our Crowdin project.
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 Visual Studio Code 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
For more installation options and troubleshooting tips, see installation. For info on how to manage Electron versions in your apps, see Electron versioning.
Platform support
Each Electron release provides binaries for macOS, Windows, and Linux.
- macOS (Monterey and up): Electron provides 64-bit Intel and Apple Silicon / ARM binaries for macOS.
- Windows (Windows 10 and up): Electron provides
ia32(x86),x64(amd64), andarm64binaries for Windows. Windows on ARM support was added in Electron 5.0.8. Support for Windows 7, 8 and 8.1 was removed in Electron 23, in line with Chromium's Windows deprecation policy. - Linux: The prebuilt binaries of Electron are built on Ubuntu 22.04. They have also been verified to work on:
- Ubuntu 18.04 and newer
- Fedora 32 and newer
- Debian 10 and newer
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.
Resources for learning Electron
- electronjs.org/docs - All of Electron's documentation
- electron/fiddle - A tool to build, run, and package small Electron experiments
- electronjs.org/community#boilerplates - Sample starter apps created by the community
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('node:child_process')
// will print something similar to /Users/maf/.../Electron
console.log(electron)
// spawn Electron
const child = proc.spawn(electron)
Mirrors
See the Advanced Installation Instructions to learn how to use a custom mirror.
Documentation translations
We crowdsource translations for our documentation via Crowdin. We currently accept translations for Chinese (Simplified), French, German, Japanese, Portuguese, Russian, and Spanish.
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 on the Community page.
License
When using Electron logos, make sure to follow OpenJS Foundation Trademark Policy.