electron-types 43.4.0 → 43.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -14,11 +14,11 @@ The official `electron` package is ~200MB because it includes the Electron binar
14
14
  Since this package only provides TypeScript types, install it as a dev dependency. **Install the version that matches your Electron version** (see [Version Matching](#version-matching)):
15
15
 
16
16
  ```bash
17
- npm install -D electron-types@43.4.0
17
+ npm install -D electron-types@43.5.0
18
18
  # or
19
- yarn add -D electron-types@43.4.0
19
+ yarn add -D electron-types@43.5.0
20
20
  # or
21
- pnpm add -D electron-types@43.4.0
21
+ pnpm add -D electron-types@43.5.0
22
22
  ```
23
23
 
24
24
  ## Usage
@@ -1,4 +1,4 @@
1
- // Type definitions for Electron 43.4.0
1
+ // Type definitions for Electron 43.5.0
2
2
  // Project: http://electronjs.org/
3
3
  // Definitions by: The Electron Team <https://github.com/electron/electron>
4
4
  // Definitions: https://github.com/electron/typescript-definitions
@@ -1561,6 +1561,11 @@ declare namespace Electron {
1561
1561
  * line, the system's single instance mechanism will be bypassed, and you have to
1562
1562
  * use this method to ensure single instance.
1563
1563
  *
1564
+ * > [!NOTE] On macOS and Linux, the second instance's command line arguments and
1565
+ * `additionalData` are sent to the primary instance in a single message that is
1566
+ * limited to 32 MB. Larger messages are dropped: this method still returns
1567
+ * `false`, but the primary instance does not emit `second-instance`.
1568
+ *
1564
1569
  * An example of activating the window of primary instance when a second instance
1565
1570
  * starts:
1566
1571
  */
@@ -1701,14 +1706,31 @@ declare namespace Electron {
1701
1706
  */
1702
1707
  setClientCertRequestPasswordHandler(handler: (clientCertRequestParams: ClientCertRequestParams) => Promise<string>): void;
1703
1708
  /**
1704
- * Sets the `.desktop` filename on Linux. This should match the base filename of
1705
- * the app's installed `.desktop` file. The `.desktop` suffix is optional.
1709
+ * Sets the `.desktop` filename on Linux. This must match the base filename of the
1710
+ * app's installed `.desktop` file. The `.desktop` suffix is optional.
1711
+ *
1712
+ * The name (without the `.desktop` suffix) is the app's identity for Linux desktop
1713
+ * integration. It should be a reverse-DNS style ID such as `com.example.MyApp`,
1714
+ * following the desktop entry naming conventions. This value is used as:
1715
+ *
1716
+ * * the XDG application ID (`app_id`) on Wayland and `WM_CLASS` on X11, used to
1717
+ * match the app's icon and window grouping.
1718
+ * * the app ID that `xdg-desktop-portal` reports to portal backends such as
1719
+ * GlobalShortcuts.
1720
+ *
1721
+ * Portals increasingly enforce this identity. If the name is not a valid
1722
+ * reverse-DNS ID or does not match an installed `.desktop` file:
1706
1723
  *
1707
- * This value is used to determine the default XDG application ID on Wayland and
1708
- * `WM_CLASS` on X11. If it is not set, Electron will attempt to infer a name, but
1709
- * it may not match the packaged app's actual `.desktop` file. This could result in
1710
- * the app showing a generic icon or failing to respond to global keyboard
1711
- * shortcuts.
1724
+ * * GNOME 50.0/50.1 (Ubuntu 26.04) rejects `globalShortcut` binds with
1725
+ * `org.freedesktop.portal.Error.NotAllowed` with no error surfaced to the app
1726
+ * (see #52218).
1727
+ * * `xdg-desktop-portal` 1.21 and later refuses portal sessions for app IDs it
1728
+ * cannot resolve to a `.desktop` file.
1729
+ *
1730
+ * If this value is not set and `desktopName` is not present in `package.json`,
1731
+ * Electron falls back to a lowercased, hyphenated slug of the app's name (e.g. `My
1732
+ * App` → `my-app.desktop`), which is unlikely to be a valid portal identity —
1733
+ * packaged apps should always set it explicitly.
1712
1734
  *
1713
1735
  * This API must be called before the `ready` event. The value can also be set
1714
1736
  * using `desktopName` in `package.json`.
@@ -9637,6 +9659,8 @@ declare namespace Electron {
9637
9659
  * or just displayed.
9638
9660
  *
9639
9661
  * This property can be dynamically changed.
9662
+ *
9663
+ * @platform linux,win32
9640
9664
  */
9641
9665
  registerAccelerator: boolean;
9642
9666
  /**
@@ -20372,6 +20396,13 @@ declare namespace Electron {
20372
20396
  * another value by including an `=`, followed by the value. Special values `yes`
20373
20397
  * and `1` are interpreted as `true`, while `no` and `0` are interpreted as
20374
20398
  * `false`.
20399
+ *
20400
+ * Security-critical preferences cannot be used to make the guest less secure than
20401
+ * its embedder. When the embedder has any of `contextIsolation`, `javascript`,
20402
+ * `nodeIntegration`, `nodeIntegrationInWorker`, `sandbox`,
20403
+ * `nodeIntegrationInSubFrames` or `enableWebSQL` set to its more secure value, the
20404
+ * guest inherits that value and the corresponding `webpreferences` entry is
20405
+ * ignored.
20375
20406
  */
20376
20407
  webpreferences: string;
20377
20408
  }
package/dist/version.json CHANGED
@@ -1,4 +1,4 @@
1
1
  {
2
- "electronVersion": "43.4.0",
3
- "extractedAt": "2026-08-12T00:27:38.898Z"
2
+ "electronVersion": "43.5.0",
3
+ "extractedAt": "2026-08-31T03:17:07.594Z"
4
4
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "electron-types",
3
- "version": "43.4.0",
3
+ "version": "43.5.0",
4
4
  "type": "module",
5
5
  "description": "TypeScript type definitions extracted from the electron package",
6
6
  "types": "./dist/electron.d.ts",