f111adcfc0
* build: use Yarn JsZipImpl for node-modules link step Patch the vendored .yarn/releases/yarn-4.12.0.cjs so the node-modules (and pnpm-loose) linker constructs its read-only ZipOpenFS with customZipImplementation = JsZipImpl instead of the default WASM LibZipImpl. LibZipImpl loads each cache zip fully into the Emscripten WASM heap and malloc's a WASM buffer per file read. With up to 80 zips held open, the 32-bit arm32v7 test container intermittently fails to allocate the ~9 MB buffer for typescript/lib/typescript.js. Yarn's cross-FS copyFilePromise swallows the real error and surfaces it as a generic "EINVAL: invalid argument, copyfile", which has been failing ~1-in-3 linux-arm test shards at Install Dependencies since 2026-04-13. JsZipImpl opens zips by fd, reads only the central directory, and pulls individual entries into plain Node Buffers — no WASM heap involved. There is no .yarnrc.yml or env knob for this, so the vendored release is edited directly. .claude/README.md documents the patch and how to re-apply it on Yarn upgrades. Refs: yarnpkg/berry#3972, yarnpkg/berry#6722, yarnpkg/berry#6550 Co-authored-by: Sam Attard <sattard@anthropic.com> * docs: move JsZipImpl patch notes to .yarn/README.md Relocate the patch rationale next to the vendored release it documents, reword the intro for its new home, and update the header comment in yarn-4.12.0.cjs to point at .yarn/README.md. 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.