9d194e28ab
* ci: build a patched siso for Windows builds The Windows Chromium builds intermittently fail during manifest load with 'The parameter is incorrect.' (ERROR_INVALID_PARAMETER) out of bindflt.sys. Root cause is a handle-relative NtCreateFile race in siso/toolsupport/ninjautil/file_parser.go, which opens each subninja twice — once in the outer goroutine and once more per chunk for ReadAt. (*os.File).ReadAt is documented as safe for concurrent use, so the extra open is redundant and removing it both halves the CreateFileW calls per subninja and sidesteps the race. Add a new build-siso-windows job on ubuntu-latest (runs in parallel with checkout-windows) that: - reads chromium_version from DEPS and pulls the matching siso_version SHA from the Chromium mirror's DEPS at that ref - shallow-clones chromium.googlesource.com/build at that SHA - applies the in-tree patches under .github/siso-patches/ via git am - cross-compiles siso.exe for windows/amd64 - caches the binary keyed on siso SHA + sha256 of the patches, so subsequent runs hit the cache and skip the clone/patch/build steps - uploads the result as a siso-windows-amd64 artifact The Windows build jobs now depend on build-siso-windows, download the artifact into $RUNNER_TEMP/siso, and export SISO_PATH, which depot_tools/siso.py already honors. Mirrored into windows-publish.yml and the regenerated pipeline-segment-electron-publish.yml so release builds pick it up too. Notes: none Co-authored-by: Sam Attard <sattard@anthropic.com> * ci: extract siso build into a reusable workflow segment Move the build-siso-windows job body into pipeline-segment-build-siso-windows.yml and call it from both build.yml and windows-publish.yml via workflow_call. Also pin actions/cache to v5.0.5 and add version comments next to the action SHAs introduced by this change. Co-authored-by: Sam Attard <sattard@anthropic.com> --------- Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com> Co-authored-by: Sam Attard <sattard@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.