claude[bot]andClaude Opus 5.5
ffbe71f787
* build: disable native window occlusion for Windows PGO collection Since the Chromium 157 roll, native window occlusion marks the benchmark window as occluded on the hosted Windows arm64 runner, so the page reports itself hidden and the rAF-driven browser benchmarks never start. Minimizing the console window (#54845) did not help. Launching the instrumented Electron with CalculateNativeWinOcclusion disabled keeps the shown window visible and only removes browser-side occlusion tracking from the profile. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMnZca8hbAx3iAsLvGkMzk * build: only disable native window occlusion for Windows arm64 PGO collection x64 collects fine with native window occlusion tracking on, so keep it enabled there. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMnZca8hbAx3iAsLvGkMzk * build: dismiss first sign-in windows before Windows PGO collection The windows-11-arm runner image leaves its first sign-in privacy settings window full screen over the desktop. Since Chromium 157, native occlusion tracking counts it as covering the benchmark window, so the page goes hidden and the benchmarks never start. Copy the spec pipeline's step that dismisses those windows into the PGO collect segment, and drop the CalculateNativeWinOcclusion opt-out so profiles are collected with occlusion tracking on, as before. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMnZca8hbAx3iAsLvGkMzk * build: share the first sign-in dismiss step as a composite action Move the "Dismiss first sign-in windows (Windows)" step from the spec pipeline into .github/actions/dismiss-windows-first-sign-in so the spec and PGO collect segments run the same script instead of two copies. The script is unchanged apart from taking the WSL terminal minimizer's duration from a minimizer-seconds input (3600 for specs, 19800 for PGO collection so it outlasts the 330 minute collect step). The callers keep timeout-minutes and continue-on-error, which composite steps do not support. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMnZca8hbAx3iAsLvGkMzk --------- Co-authored-by: Claude <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 (Ventura and up): Electron provides 64-bit Intel and Apple Silicon / ARM binaries for macOS.
- Windows (Windows 10 and up): Electron provides
x64(amd64) andarm64binaries for Windows. - Linux: Electron provides
x64(amd64) andarm64binaries for Linux. Electron supports major Linux distributions (e.g., Ubuntu, Fedora, Debian) in versions that are still supported by both Chromium and the distro maker (without requiring a paid subscription). The prebuilt binaries are built on Ubuntu.
In general, Electron tries to align with Chromium on platform support.
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
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.