claude[bot]andClaude Opus 5.5
27e39e926c
* fix: use upstream's File System Access path matcher Electron kept its own copy of ShouldBlockAccessToPath() and the Windows MaybeIsLocalUNCPath() helpers. That copy never evaluated the suffix block rules, so the kBlockWrite rules for .git/hooks, .git/config and .git/modules were not enforced, and it lacked the hypervisor host-share servers (mac, psf, vmware-host, .host, vboxsvr, vboxsrv) and trailing-dot handling that upstream added in 158.0.8120.0. Extend refactor_expose_file_system_access_blocklist.patch to move upstream's ShouldBlockAccessToPath() and its UNC helpers verbatim into chrome_file_system_access_blocklist.cc, exposed as a static member of ChromeFileSystemAccessPermissionContext, and call it from Electron with the access trigger so kBlockWrite rules only apply to save and programmatic write operations, matching Chrome. Future upstream changes to the matcher now conflict on roll instead of drifting. This replaces Electron's stricter UNC checks with upstream's: '_' is now allowed in UNC server names, and only drive (X$) and ADMIN$/IPC$/PRINT$/FAX$ admin shares are blocked rather than every '$'-suffixed share. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MtuMgvwAcw7t9Q6HEB31Vx * test: cover Windows UNC classification in the File System Access blocklist Shares a fixture directory over loopback SMB and pastes it under different UNC server and share names, checking that local server names (localhost, 127.0.0.1, and a trailing-dot localhost when it resolves) and drive admin shares are blocked while other servers and non-admin hidden shares are not. The hidden share and trailing-dot cases pin down the intentional changes from Electron's previous matcher. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MtuMgvwAcw7t9Q6HEB31Vx * test: fix the UNC spec's localhost case and share names A file URL drops a "localhost" host, so pasting \\localhost\share reached Chromium as a path with no server. Drop that case; 127.0.0.1 and the trailing-dot localhost still cover local server names. Keep share names to 12 characters so net share doesn't stop to ask about MS-DOS clients, and answer that prompt anyway in case it appears. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MtuMgvwAcw7t9Q6HEB31Vx --------- 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.