Author: saqibkhan

  • SystemPreferences

    Get system preferences.

    Process: MainUtility

    const { systemPreferences } = require('electron')
    console.log(systemPreferences.isAeroGlassEnabled())

    Events

    The systemPreferences object emits the following events:

    Event: ‘accent-color-changed’ Windows

    Returns:

    • event Event
    • newColor string – The new RGBA color the user assigned to be their system accent color.

    Event: ‘color-changed’ Windows

    Returns:

    • event Event

    Methods

    systemPreferences.isSwipeTrackingFromScrollEventsEnabled() macOS

    Returns boolean – Whether the Swipe between pages setting is on.

    systemPreferences.postNotification(event, userInfo[, deliverImmediately]) macOS

    • event string
    • userInfo Record<string, any>
    • deliverImmediately boolean (optional) – true to post notifications immediately even when the subscribing app is inactive.

    Posts event as native notifications of macOS. The userInfo is an Object that contains the user information dictionary sent along with the notification.

    systemPreferences.postLocalNotification(event, userInfo) macOS

    • event string
    • userInfo Record<string, any>

    Posts event as native notifications of macOS. The userInfo is an Object that contains the user information dictionary sent along with the notification.

    systemPreferences.postWorkspaceNotification(event, userInfo) macOS

    • event string
    • userInfo Record<string, any>

    Posts event as native notifications of macOS. The userInfo is an Object that contains the user information dictionary sent along with the notification.

    systemPreferences.subscribeNotification(event, callback) macOS

    • event string | null
    • callback Function
      • event string
      • userInfo Record<string, unknown>
      • object string

    Returns number – The ID of this subscription

    Subscribes to native notifications of macOS, callback will be called with callback(event, userInfo) when the corresponding event happens. The userInfo is an Object that contains the user information dictionary sent along with the notification. The object is the sender of the notification, and only supports NSString values for now.

    The id of the subscriber is returned, which can be used to unsubscribe the event.

    Under the hood this API subscribes to NSDistributedNotificationCenter, example values of event are:

    • AppleInterfaceThemeChangedNotification
    • AppleAquaColorVariantChanged
    • AppleColorPreferencesChangedNotification
    • AppleShowScrollBarsSettingChanged

    If event is null, the NSDistributedNotificationCenter doesn’t use it as criteria for delivery to the observer. See docs for more information.

    systemPreferences.subscribeLocalNotification(event, callback) macOS

    • event string | null
    • callback Function
      • event string
      • userInfo Record<string, unknown>
      • object string

    Returns number – The ID of this subscription

    Same as subscribeNotification, but uses NSNotificationCenter for local defaults. This is necessary for events such as NSUserDefaultsDidChangeNotification.

    If event is null, the NSNotificationCenter doesn’t use it as criteria for delivery to the observer. See docs for more information.

    systemPreferences.subscribeWorkspaceNotification(event, callback) macOS

    • event string | null
    • callback Function
      • event string
      • userInfo Record<string, unknown>
      • object string

    Returns number – The ID of this subscription

    Same as subscribeNotification, but uses NSWorkspace.sharedWorkspace.notificationCenter. This is necessary for events such as NSWorkspaceDidActivateApplicationNotification.

    If event is null, the NSWorkspaceNotificationCenter doesn’t use it as criteria for delivery to the observer. See docs for more information.

    systemPreferences.unsubscribeNotification(id) macOS

    • id Integer

    Removes the subscriber with id.

    systemPreferences.unsubscribeLocalNotification(id) macOS

    • id Integer

    Same as unsubscribeNotification, but removes the subscriber from NSNotificationCenter.

    systemPreferences.unsubscribeWorkspaceNotification(id) macOS

    • id Integer

    Same as unsubscribeNotification, but removes the subscriber from NSWorkspace.sharedWorkspace.notificationCenter.

    systemPreferences.registerDefaults(defaults) macOS

    • defaults Record<string, string | boolean | number> – a dictionary of (key: value) user defaults

    Add the specified defaults to your application’s NSUserDefaults.

    systemPreferences.getUserDefault<Type extends keyof UserDefaultTypes>(key, type) macOS

    • key string
    • type Type – Can be stringbooleanintegerfloatdoubleurlarray or dictionary.

    Returns UserDefaultTypes[Type] – The value of key in NSUserDefaults.

    Some popular key and types are:

    • AppleInterfaceStylestring
    • AppleAquaColorVariantinteger
    • AppleHighlightColorstring
    • AppleShowScrollBarsstring
    • NSNavRecentPlacesarray
    • NSPreferredWebServicesdictionary
    • NSUserDictionaryReplacementItemsarray

    systemPreferences.setUserDefault<Type extends keyof UserDefaultTypes>(key, type, value) macOS

    • key string
    • type Type – Can be stringbooleanintegerfloatdoubleurlarray or dictionary.
    • value UserDefaultTypes[Type]

    Set the value of key in NSUserDefaults.

    Note that type should match actual type of value. An exception is thrown if they don’t.

    Some popular key and types are:

    • ApplePressAndHoldEnabledboolean

    systemPreferences.removeUserDefault(key) macOS

    • key string

    Removes the key in NSUserDefaults. This can be used to restore the default or global value of a key previously set with setUserDefault.

    systemPreferences.isAeroGlassEnabled() Windows

    Returns boolean – true if DWM composition (Aero Glass) is enabled, and false otherwise.

    An example of using it to determine if you should create a transparent window or not (transparent windows won’t work correctly when DWM composition is disabled):

    const { BrowserWindow, systemPreferences } = require('electron')
    const browserOptions = { width: 1000, height: 800 }

    // Make the window transparent only if the platform supports it.
    if (process.platform !== 'win32' || systemPreferences.isAeroGlassEnabled()) {
    browserOptions.transparent = true
    browserOptions.frame = false
    }

    // Create the window.
    const win = new BrowserWindow(browserOptions)

    // Navigate.
    if (browserOptions.transparent) {
    win.loadFile('index.html')
    } else {
    // No transparency, so we load a fallback that uses basic styles.
    win.loadFile('fallback.html')
    }

    systemPreferences.getAccentColor() Windows macOS

    Returns string – The users current system wide accent color preference in RGBA hexadecimal form.

    const color = systemPreferences.getAccentColor() // "aabbccdd"
    const red = color.substr(0, 2) // "aa"
    const green = color.substr(2, 2) // "bb"
    const blue = color.substr(4, 2) // "cc"
    const alpha = color.substr(6, 2) // "dd"

    This API is only available on macOS 10.14 Mojave or newer.

    systemPreferences.getColor(color) Windows macOS

    • color string – One of the following values:
      • On Windows:
        • 3d-dark-shadow – Dark shadow for three-dimensional display elements.
        • 3d-face – Face color for three-dimensional display elements and for dialog box backgrounds.
        • 3d-highlight – Highlight color for three-dimensional display elements.
        • 3d-light – Light color for three-dimensional display elements.
        • 3d-shadow – Shadow color for three-dimensional display elements.
        • active-border – Active window border.
        • active-caption – Active window title bar. Specifies the left side color in the color gradient of an active window’s title bar if the gradient effect is enabled.
        • active-caption-gradient – Right side color in the color gradient of an active window’s title bar.
        • app-workspace – Background color of multiple document interface (MDI) applications.
        • button-text – Text on push buttons.
        • caption-text – Text in caption, size box, and scroll bar arrow box.
        • desktop – Desktop background color.
        • disabled-text – Grayed (disabled) text.
        • highlight – Item(s) selected in a control.
        • highlight-text – Text of item(s) selected in a control.
        • hotlight – Color for a hyperlink or hot-tracked item.
        • inactive-border – Inactive window border.
        • inactive-caption – Inactive window caption. Specifies the left side color in the color gradient of an inactive window’s title bar if the gradient effect is enabled.
        • inactive-caption-gradient – Right side color in the color gradient of an inactive window’s title bar.
        • inactive-caption-text – Color of text in an inactive caption.
        • info-background – Background color for tooltip controls.
        • info-text – Text color for tooltip controls.
        • menu – Menu background.
        • menu-highlight – The color used to highlight menu items when the menu appears as a flat menu.
        • menubar – The background color for the menu bar when menus appear as flat menus.
        • menu-text – Text in menus.
        • scrollbar – Scroll bar gray area.
        • window – Window background.
        • window-frame – Window frame.
        • window-text – Text in windows.
      • On macOS
        • control-background – The background of a large interface element, such as a browser or table.
        • control – The surface of a control.
        • control-text -The text of a control that isn’t disabled.
        • disabled-control-text – The text of a control that’s disabled.
        • find-highlight – The color of a find indicator.
        • grid – The gridlines of an interface element such as a table.
        • header-text – The text of a header cell in a table.
        • highlight – The virtual light source onscreen.
        • keyboard-focus-indicator – The ring that appears around the currently focused control when using the keyboard for interface navigation.
        • label – The text of a label containing primary content.
        • link – A link to other content.
        • placeholder-text – A placeholder string in a control or text view.
        • quaternary-label – The text of a label of lesser importance than a tertiary label such as watermark text.
        • scrubber-textured-background – The background of a scrubber in the Touch Bar.
        • secondary-label – The text of a label of lesser importance than a normal label such as a label used to represent a subheading or additional information.
        • selected-content-background – The background for selected content in a key window or view.
        • selected-control – The surface of a selected control.
        • selected-control-text – The text of a selected control.
        • selected-menu-item-text – The text of a selected menu.
        • selected-text-background – The background of selected text.
        • selected-text – Selected text.
        • separator – A separator between different sections of content.
        • shadow – The virtual shadow cast by a raised object onscreen.
        • tertiary-label – The text of a label of lesser importance than a secondary label such as a label used to represent disabled text.
        • text-background – Text background.
        • text – The text in a document.
        • under-page-background – The background behind a document’s content.
        • unemphasized-selected-content-background – The selected content in a non-key window or view.
        • unemphasized-selected-text-background – A background for selected text in a non-key window or view.
        • unemphasized-selected-text – Selected text in a non-key window or view.
        • window-background – The background of a window.
        • window-frame-text – The text in the window’s titlebar area.

    Returns string – The system color setting in RGBA hexadecimal form (#RRGGBBAA). See the Windows docs and the macOS docs for more details.

    The following colors are only available on macOS 10.14: find-highlightselected-content-backgroundseparatorunemphasized-selected-content-backgroundunemphasized-selected-text-background, and unemphasized-selected-text.

    systemPreferences.getSystemColor(color) macOS

    • color string – One of the following values:
      • blue
      • brown
      • gray
      • green
      • orange
      • pink
      • purple
      • red
      • yellow

    Returns string – The standard system color formatted as #RRGGBBAA.

    Returns one of several standard system colors that automatically adapt to vibrancy and changes in accessibility settings like ‘Increase contrast’ and ‘Reduce transparency’. See Apple Documentation for more details.

    systemPreferences.getEffectiveAppearance() macOS

    Returns string – Can be darklight or unknown.

    Gets the macOS appearance setting that is currently applied to your application, maps to NSApplication.effectiveAppearance

    systemPreferences.canPromptTouchID() macOS

    Returns boolean – whether or not this device has the ability to use Touch ID.

    systemPreferences.promptTouchID(reason) macOS

    • reason string – The reason you are asking for Touch ID authentication

    Returns Promise<void> – resolves if the user has successfully authenticated with Touch ID.

    const { systemPreferences } = require('electron')

    systemPreferences.promptTouchID('To get consent for a Security-Gated Thing').then(success => {
    console.log('You have successfully authenticated with Touch ID!')
    }).catch(err => {
    console.log(err)
    })

    This API itself will not protect your user data; rather, it is a mechanism to allow you to do so. Native apps will need to set Access Control Constants like kSecAccessControlUserPresence on their keychain entry so that reading it would auto-prompt for Touch ID biometric consent. This could be done with node-keytar, such that one would store an encryption key with node-keytar and only fetch it if promptTouchID() resolves.

    systemPreferences.isTrustedAccessibilityClient(prompt) macOS

    • prompt boolean – whether or not the user will be informed via prompt if the current process is untrusted.

    Returns boolean – true if the current process is a trusted accessibility client and false if it is not.

    systemPreferences.getMediaAccessStatus(mediaType) Windows macOS

    • mediaType string – Can be microphonecamera or screen.

    Returns string – Can be not-determinedgranteddeniedrestricted or unknown.

    This user consent was not required on macOS 10.13 High Sierra so this method will always return granted. macOS 10.14 Mojave or higher requires consent for microphone and camera access. macOS 10.15 Catalina or higher requires consent for screen access.

    Windows 10 has a global setting controlling microphone and camera access for all win32 applications. It will always return granted for screen and for all media types on older versions of Windows.

    systemPreferences.askForMediaAccess(mediaType) macOS

    • mediaType string – the type of media being requested; can be microphonecamera.

    Returns Promise<boolean> – A promise that resolves with true if consent was granted and false if it was denied. If an invalid mediaType is passed, the promise will be rejected. If an access request was denied and later is changed through the System Preferences pane, a restart of the app will be required for the new permissions to take effect. If access has already been requested and denied, it must be changed through the preference pane; an alert will not pop up and the promise will resolve with the existing access status.

    Important: In order to properly leverage this API, you must set the NSMicrophoneUsageDescription and NSCameraUsageDescription strings in your app’s Info.plist file. The values for these keys will be used to populate the permission dialogs so that the user will be properly informed as to the purpose of the permission request. See Electron Application Distribution for more information about how to set these in the context of Electron.

    This user consent was not required until macOS 10.14 Mojave, so this method will always return true if your system is running 10.13 High Sierra.

    systemPreferences.getAnimationSettings()

    Returns Object:

    • shouldRenderRichAnimation boolean – Returns true if rich animations should be rendered. Looks at session type (e.g. remote desktop) and accessibility settings to give guidance for heavy animations.
    • scrollAnimationsEnabledBySystem boolean – Determines on a per-platform basis whether scroll animations (e.g. produced by home/end key) should be enabled.
    • prefersReducedMotion boolean – Determines whether the user desires reduced motion based on platform APIs.

    Returns an object with system animation settings.

    Properties

    systemPreferences.accessibilityDisplayShouldReduceTransparency() macOS

    boolean property which determines whether the app avoids using semitransparent backgrounds. This maps to NSWorkspace.accessibilityDisplayShouldReduceTransparency

    systemPreferences.effectiveAppearance macOS Readonly

    string property that can be darklight or unknown.

    Returns the macOS appearance setting that is currently applied to your application, maps to NSApplication.effectiveAppearance

  • Shell

    Manage files and URLs using their default applications.

    Process: MainRenderer (non-sandboxed only)

    The shell module provides functions related to desktop integration.

    An example of opening a URL in the user’s default browser:

    const { shell } = require('electron')

    shell.openExternal('https://github.com')

    Note: While the shell module can be used in the renderer process, it will not function in a sandboxed renderer.

    Methods

    The shell module has the following methods:

    shell.showItemInFolder(fullPath)

    • fullPath string

    Show the given file in a file manager. If possible, select the file.

    shell.openPath(path)

    • path string

    Returns Promise<string> – Resolves with a string containing the error message corresponding to the failure if a failure occurred, otherwise “”.

    Open the given file in the desktop’s default manner.

    shell.openExternal(url[, options])

    • url string – Max 2081 characters on windows.
    • options Object (optional)
      • activate boolean (optional) macOS – true to bring the opened application to the foreground. The default is true.
      • workingDirectory string (optional) Windows – The working directory.
      • logUsage boolean (optional) Windows – Indicates a user initiated launch that enables tracking of frequently used programs and other behaviors. The default is false.

    Returns Promise<void>

    Open the given external protocol URL in the desktop’s default manner. (For example, mailto: URLs in the user’s default mail agent).

    shell.trashItem(path)

    • path string – path to the item to be moved to the trash.

    Returns Promise<void> – Resolves when the operation has been completed. Rejects if there was an error while deleting the requested item.

    This moves a path to the OS-specific trash location (Trash on macOS, Recycle Bin on Windows, and a desktop-environment-specific location on Linux).

    shell.beep()

    Play the beep sound.

    shell.writeShortcutLink(shortcutPath[, operation], options) Windows

    • shortcutPath string
    • operation string (optional) – Default is create, can be one of following:
      • create – Creates a new shortcut, overwriting if necessary.
      • update – Updates specified properties only on an existing shortcut.
      • replace – Overwrites an existing shortcut, fails if the shortcut doesn’t exist.
    • options ShortcutDetails

    Returns boolean – Whether the shortcut was created successfully.

    Creates or updates a shortcut link at shortcutPath.

    shell.readShortcutLink(shortcutPath) Windows

    • shortcutPath string

    Returns ShortcutDetails

    Resolves the shortcut link at shortcutPath.

    An exception will be thrown when any error happens.

  • ShareMenu

    The ShareMenu class creates Share Menu on macOS, which can be used to share information from the current context to apps, social media accounts, and other services.

    For including the share menu as a submenu of other menus, please use the shareMenu role of MenuItem.

    Class: ShareMenu

    Create share menu on macOS.

    Process: Main

    new ShareMenu(sharingItem)

    • sharingItem SharingItem – The item to share.

    Creates a new share menu.

    Instance Methods

    The shareMenu object has the following instance methods:

    shareMenu.popup([options])

    • options PopupOptions (optional)
      • browserWindow BrowserWindow (optional) – Default is the focused window.
      • x number (optional) – Default is the current mouse cursor position. Must be declared if y is declared.
      • y number (optional) – Default is the current mouse cursor position. Must be declared if x is declared.
      • positioningItem number (optional) macOS – The index of the menu item to be positioned under the mouse cursor at the specified coordinates. Default is -1.
      • callback Function (optional) – Called when menu is closed.

    Pops up this menu as a context menu in the BrowserWindow.

    shareMenu.closePopup([browserWindow])

    • browserWindow BrowserWindow (optional) – Default is the focused window.

    Closes the context menu in the browserWindow.

  • Session

    Manage browser sessions, cookies, cache, proxy settings, etc.

    Process: Main

    The session module can be used to create new Session objects.

    You can also access the session of existing pages by using the session property of WebContents, or from the session module.

    const { BrowserWindow } = require('electron')

    const win = new BrowserWindow({ width: 800, height: 600 })
    win.loadURL('https://github.com')

    const ses = win.webContents.session
    console.log(ses.getUserAgent())

    Methods

    The session module has the following methods:

    session.fromPartition(partition[, options])

    • partition string
    • options Object (optional)
      • cache boolean – Whether to enable cache.

    Returns Session – A session instance from partition string. When there is an existing Session with the same partition, it will be returned; otherwise a new Session instance will be created with options.

    If partition starts with persist:, the page will use a persistent session available to all pages in the app with the same partition. if there is no persist: prefix, the page will use an in-memory session. If the partition is empty then default session of the app will be returned.

    To create a Session with options, you have to ensure the Session with the partition has never been used before. There is no way to change the options of an existing Session object.

    session.fromPath(path[, options])

    • path string
    • options Object (optional)
      • cache boolean – Whether to enable cache.

    Returns Session – A session instance from the absolute path as specified by the path string. When there is an existing Session with the same absolute path, it will be returned; otherwise a new Session instance will be created with options. The call will throw an error if the path is not an absolute path. Additionally, an error will be thrown if an empty string is provided.

    To create a Session with options, you have to ensure the Session with the path has never been used before. There is no way to change the options of an existing Session object.

    Properties

    The session module has the following properties:

    session.defaultSession

    Session object, the default session object of the app.

    Class: Session

    Get and set properties of a session.

    Process: Main
    This class is not exported from the 'electron' module. It is only available as a return value of other methods in the Electron API.

    You can create a Session object in the session module:

    const { session } = require('electron')
    const ses = session.fromPartition('persist:name')
    console.log(ses.getUserAgent())

    Instance Events

    The following events are available on instances of Session:

    Event: ‘will-download’

    Returns:

    Emitted when Electron is about to download item in webContents.

    Calling event.preventDefault() will cancel the download and item will not be available from next tick of the process.

    const { session } = require('electron')
    session.defaultSession.on('will-download', (event, item, webContents) => {
    event.preventDefault()
    require('got')(item.getURL()).then((response) => {
    require('node:fs').writeFileSync('/somewhere', response.body)
    })
    })

    Event: ‘extension-loaded’

    Returns:

    Emitted after an extension is loaded. This occurs whenever an extension is added to the “enabled” set of extensions. This includes:

    • Extensions being loaded from Session.loadExtension.
    • Extensions being reloaded:

    Event: ‘extension-unloaded’

    Returns:

    Emitted after an extension is unloaded. This occurs when Session.removeExtension is called.

    Event: ‘extension-ready’

    Returns:

    Emitted after an extension is loaded and all necessary browser state is initialized to support the start of the extension’s background page.

    Event: ‘file-system-access-restricted’

    Returns:

    • event Event
    • details Object
      • origin string – The origin that initiated access to the blocked path.
      • isDirectory boolean – Whether or not the path is a directory.
      • path string – The blocked path attempting to be accessed.
    • callback Function
      • action string – The action to take as a result of the restricted path access attempt.
        • allow – This will allow path to be accessed despite restricted status.
        • deny – This will block the access request and trigger an AbortError.
        • tryAgain – This will open a new file picker and allow the user to choose another path.
    const { app, dialog, BrowserWindow, session } = require('electron')

    async function createWindow () {
    const mainWindow = new BrowserWindow()

    await mainWindow.loadURL('https://buzzfeed.com')

    session.defaultSession.on('file-system-access-restricted', async (e, details, callback) => {
    const { origin, path } = details
    const { response } = await dialog.showMessageBox({
    message: Are you sure you want ${origin} to open restricted path ${path}?,
    title: 'File System Access Restricted',
    buttons: ['Choose a different folder', 'Allow', 'Cancel'],
    cancelId: 2
    })

    if (response === 0) {
    callback('tryAgain')
    } else if (response === 1) {
    callback('allow')
    } else {
    callback('deny')
    }
    })

    mainWindow.webContents.executeJavaScript(<br> window.showDirectoryPicker({<br> id: 'electron-demo',<br> mode: 'readwrite',<br> startIn: 'downloads',<br> }).catch(e =&gt; {<br> console.log(e)<br> }), true
    )
    }

    app.whenReady().then(() => {
    createWindow()

    app.on('activate', () => {
    if (BrowserWindow.getAllWindows().length === 0) createWindow()
    })
    })

    app.on('window-all-closed', function () {
    if (process.platform !== 'darwin') app.quit()
    })

    Event: ‘preconnect’

    Returns:

    • event Event
    • preconnectUrl string – The URL being requested for preconnection by the renderer.
    • allowCredentials boolean – True if the renderer is requesting that the connection include credentials (see the spec for more details.)

    Emitted when a render process requests preconnection to a URL, generally due to a resource hint.

    Event: ‘spellcheck-dictionary-initialized’

    Returns:

    • event Event
    • languageCode string – The language code of the dictionary file

    Emitted when a hunspell dictionary file has been successfully initialized. This occurs after the file has been downloaded.

    Event: ‘spellcheck-dictionary-download-begin’

    Returns:

    • event Event
    • languageCode string – The language code of the dictionary file

    Emitted when a hunspell dictionary file starts downloading

    Event: ‘spellcheck-dictionary-download-success’

    Returns:

    • event Event
    • languageCode string – The language code of the dictionary file

    Emitted when a hunspell dictionary file has been successfully downloaded

    Event: ‘spellcheck-dictionary-download-failure’

    Returns:

    • event Event
    • languageCode string – The language code of the dictionary file

    Emitted when a hunspell dictionary file download fails. For details on the failure you should collect a netlog and inspect the download request.

    Event: ‘select-hid-device’

    Returns:

    • event Event
    • details Object
    • callback Function
      • deviceId string | null (optional)

    Emitted when a HID device needs to be selected when a call to navigator.hid.requestDevice is made. callback should be called with deviceId to be selected; passing no arguments to callback will cancel the request. Additionally, permissioning on navigator.hid can be further managed by using ses.setPermissionCheckHandler(handler) and ses.setDevicePermissionHandler(handler).

    const { app, BrowserWindow } = require('electron')

    let win = null

    app.whenReady().then(() => {
    win = new BrowserWindow()

    win.webContents.session.setPermissionCheckHandler((webContents, permission, requestingOrigin, details) => {
    if (permission === 'hid') {
    // Add logic here to determine if permission should be given to allow HID selection
    return true
    }
    return false
    })

    // Optionally, retrieve previously persisted devices from a persistent store
    const grantedDevices = fetchGrantedDevices()

    win.webContents.session.setDevicePermissionHandler((details) => {
    if (new URL(details.origin).hostname === 'some-host' && details.deviceType === 'hid') {
    if (details.device.vendorId === 123 && details.device.productId === 345) {
    // Always allow this type of device (this allows skipping the call to navigator.hid.requestDevice first)
    return true
    }

    // Search through the list of devices that have previously been granted permission
    return grantedDevices.some((grantedDevice) => {
    return grantedDevice.vendorId === details.device.vendorId &&
    grantedDevice.productId === details.device.productId &&
    grantedDevice.serialNumber && grantedDevice.serialNumber === details.device.serialNumber
    })
    }
    return false
    })

    win.webContents.session.on('select-hid-device', (event, details, callback) => {
    event.preventDefault()
    const selectedDevice = details.deviceList.find((device) => {
    return device.vendorId === 9025 && device.productId === 67
    })
    callback(selectedDevice?.deviceId)
    })
    })

    Event: ‘hid-device-added’

    Returns:

    Emitted after navigator.hid.requestDevice has been called and select-hid-device has fired if a new device becomes available before the callback from select-hid-device is called. This event is intended for use when using a UI to ask users to pick a device so that the UI can be updated with the newly added device.

    Event: ‘hid-device-removed’

    Returns:

    Emitted after navigator.hid.requestDevice has been called and select-hid-device has fired if a device has been removed before the callback from select-hid-device is called. This event is intended for use when using a UI to ask users to pick a device so that the UI can be updated to remove the specified device.

    Event: ‘hid-device-revoked’

    Returns:

    • event Event
    • details Object
      • device HIDDevice
      • origin string (optional) – The origin that the device has been revoked from.

    Emitted after HIDDevice.forget() has been called. This event can be used to help maintain persistent storage of permissions when setDevicePermissionHandler is used.

    Event: ‘select-serial-port’

    Returns:

    Emitted when a serial port needs to be selected when a call to navigator.serial.requestPort is made. callback should be called with portId to be selected, passing an empty string to callback will cancel the request. Additionally, permissioning on navigator.serial can be managed by using ses.setPermissionCheckHandler(handler) with the serial permission.

    const { app, BrowserWindow } = require('electron')

    let win = null

    app.whenReady().then(() => {
    win = new BrowserWindow({
    width: 800,
    height: 600
    })

    win.webContents.session.setPermissionCheckHandler((webContents, permission, requestingOrigin, details) => {
    if (permission === 'serial') {
    // Add logic here to determine if permission should be given to allow serial selection
    return true
    }
    return false
    })

    // Optionally, retrieve previously persisted devices from a persistent store
    const grantedDevices = fetchGrantedDevices()

    win.webContents.session.setDevicePermissionHandler((details) => {
    if (new URL(details.origin).hostname === 'some-host' && details.deviceType === 'serial') {
    if (details.device.vendorId === 123 && details.device.productId === 345) {
    // Always allow this type of device (this allows skipping the call to navigator.serial.requestPort first)
    return true
    }

    // Search through the list of devices that have previously been granted permission
    return grantedDevices.some((grantedDevice) => {
    return grantedDevice.vendorId === details.device.vendorId &&
    grantedDevice.productId === details.device.productId &&
    grantedDevice.serialNumber && grantedDevice.serialNumber === details.device.serialNumber
    })
    }
    return false
    })

    win.webContents.session.on('select-serial-port', (event, portList, webContents, callback) => {
    event.preventDefault()
    const selectedPort = portList.find((device) => {
    return device.vendorId === '9025' && device.productId === '67'
    })
    if (!selectedPort) {
    callback('')
    } else {
    callback(selectedPort.portId)
    }
    })
    })

    Event: ‘serial-port-added’

    Returns:

    Emitted after navigator.serial.requestPort has been called and select-serial-port has fired if a new serial port becomes available before the callback from select-serial-port is called. This event is intended for use when using a UI to ask users to pick a port so that the UI can be updated with the newly added port.

    Event: ‘serial-port-removed’

    Returns:

    Emitted after navigator.serial.requestPort has been called and select-serial-port has fired if a serial port has been removed before the callback from select-serial-port is called. This event is intended for use when using a UI to ask users to pick a port so that the UI can be updated to remove the specified port.

    Event: ‘serial-port-revoked’

    Returns:

    • event Event
    • details Object

    Emitted after SerialPort.forget() has been called. This event can be used to help maintain persistent storage of permissions when setDevicePermissionHandler is used.

    // Browser Process
    const { app, BrowserWindow } = require('electron')

    app.whenReady().then(() => {
    const win = new BrowserWindow({
    width: 800,
    height: 600
    })

    win.webContents.session.on('serial-port-revoked', (event, details) => {
    console.log(Access revoked for serial device from origin ${details.origin})
    })
    })
    // Renderer Process

    const portConnect = async () => {
    // Request a port.
    const port = await navigator.serial.requestPort()

    // Wait for the serial port to open.
    await port.open({ baudRate: 9600 })

    // ...later, revoke access to the serial port.
    await port.forget()
    }

    Event: ‘select-usb-device’

    Returns:

    • event Event
    • details Object
    • callback Function
      • deviceId string (optional)

    Emitted when a USB device needs to be selected when a call to navigator.usb.requestDevice is made. callback should be called with deviceId to be selected; passing no arguments to callback will cancel the request. Additionally, permissioning on navigator.usb can be further managed by using ses.setPermissionCheckHandler(handler) and ses.setDevicePermissionHandler(handler).

    const { app, BrowserWindow } = require('electron')

    let win = null

    app.whenReady().then(() => {
    win = new BrowserWindow()

    win.webContents.session.setPermissionCheckHandler((webContents, permission, requestingOrigin, details) => {
    if (permission === 'usb') {
    // Add logic here to determine if permission should be given to allow USB selection
    return true
    }
    return false
    })

    // Optionally, retrieve previously persisted devices from a persistent store (fetchGrantedDevices needs to be implemented by developer to fetch persisted permissions)
    const grantedDevices = fetchGrantedDevices()

    win.webContents.session.setDevicePermissionHandler((details) => {
    if (new URL(details.origin).hostname === 'some-host' && details.deviceType === 'usb') {
    if (details.device.vendorId === 123 && details.device.productId === 345) {
    // Always allow this type of device (this allows skipping the call to navigator.usb.requestDevice first)
    return true
    }

    // Search through the list of devices that have previously been granted permission
    return grantedDevices.some((grantedDevice) => {
    return grantedDevice.vendorId === details.device.vendorId &&
    grantedDevice.productId === details.device.productId &&
    grantedDevice.serialNumber && grantedDevice.serialNumber === details.device.serialNumber
    })
    }
    return false
    })

    win.webContents.session.on('select-usb-device', (event, details, callback) => {
    event.preventDefault()
    const selectedDevice = details.deviceList.find((device) => {
    return device.vendorId === 9025 && device.productId === 67
    })
    if (selectedDevice) {
    // Optionally, add this to the persisted devices (updateGrantedDevices needs to be implemented by developer to persist permissions)
    grantedDevices.push(selectedDevice)
    updateGrantedDevices(grantedDevices)
    }
    callback(selectedDevice?.deviceId)
    })
    })

    Event: ‘usb-device-added’

    Returns:

    Emitted after navigator.usb.requestDevice has been called and select-usb-device has fired if a new device becomes available before the callback from select-usb-device is called. This event is intended for use when using a UI to ask users to pick a device so that the UI can be updated with the newly added device.

    Event: ‘usb-device-removed’

    Returns:

    Emitted after navigator.usb.requestDevice has been called and select-usb-device has fired if a device has been removed before the callback from select-usb-device is called. This event is intended for use when using a UI to ask users to pick a device so that the UI can be updated to remove the specified device.

    Event: ‘usb-device-revoked’

    Returns:

    • event Event
    • details Object
      • device USBDevice
      • origin string (optional) – The origin that the device has been revoked from.

    Emitted after USBDevice.forget() has been called. This event can be used to help maintain persistent storage of permissions when setDevicePermissionHandler is used.

    Instance Methods

    The following methods are available on instances of Session:

    ses.getCacheSize()

    Returns Promise<Integer> – the session’s current cache size, in bytes.

    ses.clearCache()

    Returns Promise<void> – resolves when the cache clear operation is complete.

    Clears the session’s HTTP cache.

    ses.clearStorageData([options])

    • options Object (optional)
      • origin string (optional) – Should follow window.location.origin’s representation scheme://host:port.
      • storages string[] (optional) – The types of storages to clear, can be cookiesfilesystemindexdblocalstorageshadercachewebsqlserviceworkerscachestorage. If not specified, clear all storage types.
      • quotas string[] (optional) – The types of quotas to clear, can be temporarysyncable. If not specified, clear all quotas.

    Returns Promise<void> – resolves when the storage data has been cleared.

    ses.flushStorageData()

    Writes any unwritten DOMStorage data to disk.

    ses.setProxy(config)

    Returns Promise<void> – Resolves when the proxy setting process is complete.

    Sets the proxy settings.

    You may need ses.closeAllConnections to close currently in flight connections to prevent pooled sockets using previous proxy from being reused by future requests.

    ses.resolveHost(host, [options])

    • host string – Hostname to resolve.
    • options Object (optional)
      • queryType string (optional) – Requested DNS query type. If unspecified, resolver will pick A or AAAA (or both) based on IPv4/IPv6 settings:
        • A – Fetch only A records
        • AAAA – Fetch only AAAA records.
      • source string (optional) – The source to use for resolved addresses. Default allows the resolver to pick an appropriate source. Only affects use of big external sources (e.g. calling the system for resolution or using DNS). Even if a source is specified, results can still come from cache, resolving “localhost” or IP literals, etc. One of the following values:
        • any (default) – Resolver will pick an appropriate source. Results could come from DNS, MulticastDNS, HOSTS file, etc
        • system – Results will only be retrieved from the system or OS, e.g. via the getaddrinfo() system call
        • dns – Results will only come from DNS queries
        • mdns – Results will only come from Multicast DNS queries
        • localOnly – No external sources will be used. Results will only come from fast local sources that are available no matter the source setting, e.g. cache, hosts file, IP literal resolution, etc.
      • cacheUsage string (optional) – Indicates what DNS cache entries, if any, can be used to provide a response. One of the following values:
        • allowed (default) – Results may come from the host cache if non-stale
        • staleAllowed – Results may come from the host cache even if stale (by expiration or network changes)
        • disallowed – Results will not come from the host cache.
      • secureDnsPolicy string (optional) – Controls the resolver’s Secure DNS behavior for this request. One of the following values:
        • allow (default)
        • disable

    Returns Promise<ResolvedHost> – Resolves with the resolved IP addresses for the host.

    ses.resolveProxy(url)

    • url URL

    Returns Promise<string> – Resolves with the proxy information for url.

    ses.forceReloadProxyConfig()

    Returns Promise<void> – Resolves when the all internal states of proxy service is reset and the latest proxy configuration is reapplied if it’s already available. The pac script will be fetched from pacScript again if the proxy mode is pac_script.

    ses.setDownloadPath(path)

    • path string – The download location.

    Sets download saving directory. By default, the download directory will be the Downloads under the respective app folder.

    ses.enableNetworkEmulation(options)

    • options Object
      • offline boolean (optional) – Whether to emulate network outage. Defaults to false.
      • latency Double (optional) – RTT in ms. Defaults to 0 which will disable latency throttling.
      • downloadThroughput Double (optional) – Download rate in Bps. Defaults to 0 which will disable download throttling.
      • uploadThroughput Double (optional) – Upload rate in Bps. Defaults to 0 which will disable upload throttling.

    Emulates network with the given configuration for the session.

    const win = new BrowserWindow()

    // To emulate a GPRS connection with 50kbps throughput and 500 ms latency.
    win.webContents.session.enableNetworkEmulation({
    latency: 500,
    downloadThroughput: 6400,
    uploadThroughput: 6400
    })

    // To emulate a network outage.
    win.webContents.session.enableNetworkEmulation({ offline: true })

    ses.preconnect(options)

    • options Object
      • url string – URL for preconnect. Only the origin is relevant for opening the socket.
      • numSockets number (optional) – number of sockets to preconnect. Must be between 1 and 6. Defaults to 1.

    Preconnects the given number of sockets to an origin.

    ses.closeAllConnections()

    Returns Promise<void> – Resolves when all connections are closed.

    Note: It will terminate / fail all requests currently in flight.

    ses.fetch(input[, init])

    Returns Promise<GlobalResponse> – see Response.

    Sends a request, similarly to how fetch() works in the renderer, using Chrome’s network stack. This differs from Node’s fetch(), which uses Node.js’s HTTP stack.

    Example:

    async function example () {
    const response = await net.fetch('https://my.app')
    if (response.ok) {
    const body = await response.json()
    // ... use the result.
    }
    }

    See also net.fetch(), a convenience method which issues requests from the default session.

    See the MDN documentation for fetch() for more details.

    Limitations:

    • net.fetch() does not support the data: or blob: schemes.
    • The value of the integrity option is ignored.
    • The .type and .url values of the returned Response object are incorrect.

    By default, requests made with net.fetch can be made to custom protocols as well as file:, and will trigger webRequest handlers if present. When the non-standard bypassCustomProtocolHandlers option is set in RequestInit, custom protocol handlers will not be called for this request. This allows forwarding an intercepted request to the built-in handler. webRequest handlers will still be triggered when bypassing custom protocols.

    protocol.handle('https', (req) => {
    if (req.url === 'https://my-app.com') {
    return new Response('<body>my app</body>')
    } else {
    return net.fetch(req, { bypassCustomProtocolHandlers: true })
    }
    })

    ses.disableNetworkEmulation()

    Disables any network emulation already active for the session. Resets to the original network configuration.

    ses.setCertificateVerifyProc(proc)

    • proc Function | null
      • request Object
        • hostname string
        • certificate Certificate
        • validatedCertificate Certificate
        • isIssuedByKnownRoot boolean – true if Chromium recognises the root CA as a standard root. If it isn’t then it’s probably the case that this certificate was generated by a MITM proxy whose root has been installed locally (for example, by a corporate proxy). This should not be trusted if the verificationResult is not OK.
        • verificationResult string – OK if the certificate is trusted, otherwise an error like CERT_REVOKED.
        • errorCode Integer – Error code.
      • callback Function
        • verificationResult Integer – Value can be one of certificate error codes from here. Apart from the certificate error codes, the following special codes can be used.
          • 0 – Indicates success and disables Certificate Transparency verification.
          • -2 – Indicates failure.
          • -3 – Uses the verification result from chromium.

    Sets the certificate verify proc for session, the proc will be called with proc(request, callback) whenever a server certificate verification is requested. Calling callback(0) accepts the certificate, calling callback(-2) rejects it.

    Calling setCertificateVerifyProc(null) will revert back to default certificate verify proc.

    const { BrowserWindow } = require('electron')
    const win = new BrowserWindow()

    win.webContents.session.setCertificateVerifyProc((request, callback) => {
    const { hostname } = request
    if (hostname === 'github.com') {
    callback(0)
    } else {
    callback(-2)
    }
    })

    NOTE: The result of this procedure is cached by the network service.

    ses.setPermissionRequestHandler(handler)

    • handler Function | null
      • webContents WebContents – WebContents requesting the permission. Please note that if the request comes from a subframe you should use requestingUrl to check the request origin.
      • permission string – The type of requested permission.
        • clipboard-read – Request access to read from the clipboard.
        • clipboard-sanitized-write – Request access to write to the clipboard.
        • display-capture – Request access to capture the screen via the Screen Capture API.
        • fullscreen – Request control of the app’s fullscreen state via the Fullscreen API.
        • geolocation – Request access to the user’s location via the Geolocation API
        • idle-detection – Request access to the user’s idle state via the IdleDetector API.
        • media – Request access to media devices such as camera, microphone and speakers.
        • mediaKeySystem – Request access to DRM protected content.
        • midi – Request MIDI access in the Web MIDI API.
        • midiSysex – Request the use of system exclusive messages in the Web MIDI API.
        • notifications – Request notification creation and the ability to display them in the user’s system tray using the Notifications API
        • pointerLock – Request to directly interpret mouse movements as an input method via the Pointer Lock API. These requests always appear to originate from the main frame.
        • keyboardLock – Request capture of keypresses for any or all of the keys on the physical keyboard via the Keyboard Lock API. These requests always appear to originate from the main frame.
        • openExternal – Request to open links in external applications.
        • speaker-selection – Request to enumerate and select audio output devices via the speaker-selection permissions policy.
        • storage-access – Allows content loaded in a third-party context to request access to third-party cookies using the Storage Access API.
        • top-level-storage-access – Allow top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same related website set using the Storage Access API.
        • window-management – Request access to enumerate screens using the getScreenDetails API.
        • unknown – An unrecognized permission request.
        • fileSystem – Request access to read, write, and file management capabilities using the File System API.
      • callback Function
        • permissionGranted boolean – Allow or deny the permission.
      • details PermissionRequest | FilesystemPermissionRequest | MediaAccessPermissionRequest | OpenExternalPermissionRequest – Additional information about the permission being requested.

    Sets the handler which can be used to respond to permission requests for the session. Calling callback(true) will allow the permission and callback(false) will reject it. To clear the handler, call setPermissionRequestHandler(null). Please note that you must also implement setPermissionCheckHandler to get complete permission handling. Most web APIs do a permission check and then make a permission request if the check is denied.

    const { session } = require('electron')
    session.fromPartition('some-partition').setPermissionRequestHandler((webContents, permission, callback) => {
    if (webContents.getURL() === 'some-host' && permission === 'notifications') {
    return callback(false) // denied.
    }

    callback(true)
    })

    ses.setPermissionCheckHandler(handler)

    • handler Function | null
      • webContents (WebContents | null) – WebContents checking the permission. Please note that if the request comes from a subframe you should use requestingUrl to check the request origin. All cross origin sub frames making permission checks will pass a null webContents to this handler, while certain other permission checks such as notifications checks will always pass null. You should use embeddingOrigin and requestingOrigin to determine what origin the owning frame and the requesting frame are on respectively.
      • permission string – Type of permission check.
        • clipboard-read – Request access to read from the clipboard.
        • clipboard-sanitized-write – Request access to write to the clipboard.
        • geolocation – Access the user’s geolocation data via the Geolocation API
        • fullscreen – Control of the app’s fullscreen state via the Fullscreen API.
        • hid – Access the HID protocol to manipulate HID devices via the WebHID API.
        • idle-detection – Access the user’s idle state via the IdleDetector API.
        • media – Access to media devices such as camera, microphone and speakers.
        • mediaKeySystem – Access to DRM protected content.
        • midi – Enable MIDI access in the Web MIDI API.
        • midiSysex – Use system exclusive messages in the Web MIDI API.
        • notifications – Configure and display desktop notifications to the user with the Notifications API.
        • openExternal – Open links in external applications.
        • pointerLock – Directly interpret mouse movements as an input method via the Pointer Lock API. These requests always appear to originate from the main frame.
        • serial – Read from and write to serial devices with the Web Serial API.
        • storage-access – Allows content loaded in a third-party context to request access to third-party cookies using the Storage Access API.
        • top-level-storage-access – Allow top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same related website set using the Storage Access API.
        • usb – Expose non-standard Universal Serial Bus (USB) compatible devices services to the web with the WebUSB API.
      • requestingOrigin string – The origin URL of the permission check
      • details Object – Some properties are only available on certain permission types.
        • embeddingOrigin string (optional) – The origin of the frame embedding the frame that made the permission check. Only set for cross-origin sub frames making permission checks.
        • securityOrigin string (optional) – The security origin of the media check.
        • mediaType string (optional) – The type of media access being requested, can be videoaudio or unknown
        • requestingUrl string (optional) – The last URL the requesting frame loaded. This is not provided for cross-origin sub frames making permission checks.
        • isMainFrame boolean – Whether the frame making the request is the main frame

    Sets the handler which can be used to respond to permission checks for the session. Returning true will allow the permission and false will reject it. Please note that you must also implement setPermissionRequestHandler to get complete permission handling. Most web APIs do a permission check and then make a permission request if the check is denied. To clear the handler, call setPermissionCheckHandler(null).

    const { session } = require('electron')
    const url = require('url')
    session.fromPartition('some-partition').setPermissionCheckHandler((webContents, permission, requestingOrigin) => {
    if (new URL(requestingOrigin).hostname === 'some-host' && permission === 'notifications') {
    return true // granted
    }

    return false // denied
    })

    ses.setDisplayMediaRequestHandler(handler)

    • handler Function | null
      • request Object
        • frame WebFrameMain – Frame that is requesting access to media.
        • securityOrigin String – Origin of the page making the request.
        • videoRequested Boolean – true if the web content requested a video stream.
        • audioRequested Boolean – true if the web content requested an audio stream.
        • userGesture Boolean – Whether a user gesture was active when this request was triggered.
      • callback Function
        • streams Object
          • video Object | WebFrameMain (optional)
            • id String – The id of the stream being granted. This will usually come from a DesktopCapturerSource object.
            • name String – The name of the stream being granted. This will usually come from a DesktopCapturerSource object.
          • audio String | WebFrameMain (optional) – If a string is specified, can be loopback or loopbackWithMute. Specifying a loopback device will capture system audio, and is currently only supported on Windows. If a WebFrameMain is specified, will capture audio from that frame.
          • enableLocalEcho Boolean (optional) – If audio is a WebFrameMain and this is set to true, then local playback of audio will not be muted (e.g. using MediaRecorder to record WebFrameMain with this flag set to true will allow audio to pass through to the speakers while recording). Default is false.

    This handler will be called when web content requests access to display media via the navigator.mediaDevices.getDisplayMedia API. Use the desktopCapturer API to choose which stream(s) to grant access to.

    const { session, desktopCapturer } = require('electron')

    session.defaultSession.setDisplayMediaRequestHandler((request, callback) => {
    desktopCapturer.getSources({ types: ['screen'] }).then((sources) => {
    // Grant access to the first screen found.
    callback({ video: sources[0] })
    })
    })

    Passing a WebFrameMain object as a video or audio stream will capture the video or audio stream from that frame.

    const { session } = require('electron')

    session.defaultSession.setDisplayMediaRequestHandler((request, callback) => {
    // Allow the tab to capture itself.
    callback({ video: request.frame })
    })

    Passing null instead of a function resets the handler to its default state.

    ses.setDevicePermissionHandler(handler)

    • handler Function | null
      • details Object
        • deviceType string – The type of device that permission is being requested on, can be hidserial, or usb.
        • origin string – The origin URL of the device permission check.
        • device HIDDevice | SerialPort | USBDevice – the device that permission is being requested for.

    Sets the handler which can be used to respond to device permission checks for the session. Returning true will allow the device to be permitted and false will reject it. To clear the handler, call setDevicePermissionHandler(null). This handler can be used to provide default permissioning to devices without first calling for permission to devices (eg via navigator.hid.requestDevice). If this handler is not defined, the default device permissions as granted through device selection (eg via navigator.hid.requestDevice) will be used. Additionally, the default behavior of Electron is to store granted device permission in memory. If longer term storage is needed, a developer can store granted device permissions (eg when handling the select-hid-device event) and then read from that storage with setDevicePermissionHandler.

    const { app, BrowserWindow } = require('electron')

    let win = null

    app.whenReady().then(() => {
    win = new BrowserWindow()

    win.webContents.session.setPermissionCheckHandler((webContents, permission, requestingOrigin, details) => {
    if (permission === 'hid') {
    // Add logic here to determine if permission should be given to allow HID selection
    return true
    } else if (permission === 'serial') {
    // Add logic here to determine if permission should be given to allow serial port selection
    } else if (permission === 'usb') {
    // Add logic here to determine if permission should be given to allow USB device selection
    }
    return false
    })

    // Optionally, retrieve previously persisted devices from a persistent store
    const grantedDevices = fetchGrantedDevices()

    win.webContents.session.setDevicePermissionHandler((details) => {
    if (new URL(details.origin).hostname === 'some-host' && details.deviceType === 'hid') {
    if (details.device.vendorId === 123 && details.device.productId === 345) {
    // Always allow this type of device (this allows skipping the call to navigator.hid.requestDevice first)
    return true
    }

    // Search through the list of devices that have previously been granted permission
    return grantedDevices.some((grantedDevice) => {
    return grantedDevice.vendorId === details.device.vendorId &&
    grantedDevice.productId === details.device.productId &&
    grantedDevice.serialNumber && grantedDevice.serialNumber === details.device.serialNumber
    })
    } else if (details.deviceType === 'serial') {
    if (details.device.vendorId === 123 && details.device.productId === 345) {
    // Always allow this type of device (this allows skipping the call to navigator.hid.requestDevice first)
    return true
    }
    }
    return false
    })

    win.webContents.session.on('select-hid-device', (event, details, callback) => {
    event.preventDefault()
    const selectedDevice = details.deviceList.find((device) => {
    return device.vendorId === 9025 && device.productId === 67
    })
    callback(selectedDevice?.deviceId)
    })
    })

    ses.setUSBProtectedClassesHandler(handler)

    • handler Function | null
      • details Object
        • protectedClasses string[] – The current list of protected USB classes. Possible class values include:
          • audio
          • audio-video
          • hid
          • mass-storage
          • smart-card
          • video
          • wireless

    Sets the handler which can be used to override which USB classes are protected. The return value for the handler is a string array of USB classes which should be considered protected (eg not available in the renderer). Valid values for the array are:

    • audio
    • audio-video
    • hid
    • mass-storage
    • smart-card
    • video
    • wireless

    Returning an empty string array from the handler will allow all USB classes; returning the passed in array will maintain the default list of protected USB classes (this is also the default behavior if a handler is not defined). To clear the handler, call setUSBProtectedClassesHandler(null).

    const { app, BrowserWindow } = require('electron')

    let win = null

    app.whenReady().then(() => {
    win = new BrowserWindow()

    win.webContents.session.setUSBProtectedClassesHandler((details) => {
    // Allow all classes:
    // return []
    // Keep the current set of protected classes:
    // return details.protectedClasses
    // Selectively remove classes:
    return details.protectedClasses.filter((usbClass) => {
    // Exclude classes except for audio classes
    return usbClass.indexOf('audio') === -1
    })
    })
    })

    ses.setBluetoothPairingHandler(handler) Windows Linux

    • handler Function | null
      • details Object
        • deviceId string
        • pairingKind string – The type of pairing prompt being requested. One of the following values:
          • confirm This prompt is requesting confirmation that the Bluetooth device should be paired.
          • confirmPin This prompt is requesting confirmation that the provided PIN matches the pin displayed on the device.
          • providePin This prompt is requesting that a pin be provided for the device.
        • frame WebFrameMain
        • pin string (optional) – The pin value to verify if pairingKind is confirmPin.
      • callback Function
        • response Object
          • confirmed boolean – false should be passed in if the dialog is canceled. If the pairingKind is confirm or confirmPin, this value should indicate if the pairing is confirmed. If the pairingKind is providePin the value should be true when a value is provided.
          • pin string | null (optional) – When the pairingKind is providePin this value should be the required pin for the Bluetooth device.

    Sets a handler to respond to Bluetooth pairing requests. This handler allows developers to handle devices that require additional validation before pairing. When a handler is not defined, any pairing on Linux or Windows that requires additional validation will be automatically cancelled. macOS does not require a handler because macOS handles the pairing automatically. To clear the handler, call setBluetoothPairingHandler(null).

    const { app, BrowserWindow, session } = require('electron')
    const path = require('node:path')

    function createWindow () {
    let bluetoothPinCallback = null

    const mainWindow = new BrowserWindow({
    webPreferences: {
    preload: path.join(__dirname, 'preload.js')
    }
    })

    mainWindow.webContents.session.setBluetoothPairingHandler((details, callback) => {
    bluetoothPinCallback = callback
    // Send a IPC message to the renderer to prompt the user to confirm the pairing.
    // Note that this will require logic in the renderer to handle this message and
    // display a prompt to the user.
    mainWindow.webContents.send('bluetooth-pairing-request', details)
    })

    // Listen for an IPC message from the renderer to get the response for the Bluetooth pairing.
    mainWindow.webContents.ipc.on('bluetooth-pairing-response', (event, response) => {
    bluetoothPinCallback(response)
    })
    }

    app.whenReady().then(() => {
    createWindow()
    })

    ses.clearHostResolverCache()

    Returns Promise<void> – Resolves when the operation is complete.

    Clears the host resolver cache.

    ses.allowNTLMCredentialsForDomains(domains)

    • domains string – A comma-separated list of servers for which integrated authentication is enabled.

    Dynamically sets whether to always send credentials for HTTP NTLM or Negotiate authentication.

    const { session } = require('electron')
    // consider any url ending with example.com, foobar.com, baz
    // for integrated authentication.
    session.defaultSession.allowNTLMCredentialsForDomains('*example.com, *foobar.com, *baz')

    // consider all urls for integrated authentication.
    session.defaultSession.allowNTLMCredentialsForDomains('*')

    ses.setUserAgent(userAgent[, acceptLanguages])

    • userAgent string
    • acceptLanguages string (optional)

    Overrides the userAgent and acceptLanguages for this session.

    The acceptLanguages must a comma separated ordered list of language codes, for example "en-US,fr,de,ko,zh-CN,ja".

    This doesn’t affect existing WebContents, and each WebContents can use webContents.setUserAgent to override the session-wide user agent.

    ses.isPersistent()

    Returns boolean – Whether or not this session is a persistent one. The default webContents session of a BrowserWindow is persistent. When creating a session from a partition, session prefixed with persist: will be persistent, while others will be temporary.

    ses.getUserAgent()

    Returns string – The user agent for this session.

    ses.setSSLConfig(config)

    • config Object
      • minVersion string (optional) – Can be tls1tls1.1tls1.2 or tls1.3. The minimum SSL version to allow when connecting to remote servers. Defaults to tls1.
      • maxVersion string (optional) – Can be tls1.2 or tls1.3. The maximum SSL version to allow when connecting to remote servers. Defaults to tls1.3.
      • disabledCipherSuites Integer[] (optional) – List of cipher suites which should be explicitly prevented from being used in addition to those disabled by the net built-in policy. Supported literal forms: 0xAABB, where AA is cipher_suite[0] and BB is cipher_suite[1], as defined in RFC 2246, Section 7.4.1.2. Unrecognized but parsable cipher suites in this form will not return an error. Ex: To disable TLS_RSA_WITH_RC4_128_MD5, specify 0x0004, while to disable TLS_ECDH_ECDSA_WITH_RC4_128_SHA, specify 0xC002. Note that TLSv1.3 ciphers cannot be disabled using this mechanism.

    Sets the SSL configuration for the session. All subsequent network requests will use the new configuration. Existing network connections (such as WebSocket connections) will not be terminated, but old sockets in the pool will not be reused for new connections.

    ses.getBlobData(identifier)

    • identifier string – Valid UUID.

    Returns Promise<Buffer> – resolves with blob data.

    ses.downloadURL(url[, options])

    • url string
    • options Object (optional)
      • headers Record<string, string> (optional) – HTTP request headers.

    Initiates a download of the resource at url. The API will generate a DownloadItem that can be accessed with the will-download event.

    Note: This does not perform any security checks that relate to a page’s origin, unlike webContents.downloadURL.

    ses.createInterruptedDownload(options)

    • options Object
      • path string – Absolute path of the download.
      • urlChain string[] – Complete URL chain for the download.
      • mimeType string (optional)
      • offset Integer – Start range for the download.
      • length Integer – Total length of the download.
      • lastModified string (optional) – Last-Modified header value.
      • eTag string (optional) – ETag header value.
      • startTime Double (optional) – Time when download was started in number of seconds since UNIX epoch.

    Allows resuming cancelled or interrupted downloads from previous Session. The API will generate a DownloadItem that can be accessed with the will-download event. The DownloadItem will not have any WebContents associated with it and the initial state will be interrupted. The download will start only when the resume API is called on the DownloadItem.

    ses.clearAuthCache()

    Returns Promise<void> – resolves when the session’s HTTP authentication cache has been cleared.

    ses.setPreloads(preloads)

    • preloads string[] – An array of absolute path to preload scripts

    Adds scripts that will be executed on ALL web contents that are associated with this session just before normal preload scripts run.

    ses.getPreloads()

    Returns string[] an array of paths to preload scripts that have been registered.

    ses.setCodeCachePath(path)

    • path String – Absolute path to store the v8 generated JS code cache from the renderer.

    Sets the directory to store the generated JS code cache for this session. The directory is not required to be created by the user before this call, the runtime will create if it does not exist otherwise will use the existing directory. If directory cannot be created, then code cache will not be used and all operations related to code cache will fail silently inside the runtime. By default, the directory will be Code Cache under the respective user data folder.

    Note that by default code cache is only enabled for http(s) URLs, to enable code cache for custom protocols, codeCache: true and standard: true must be specified when registering the protocol.

    ses.clearCodeCaches(options)

    • options Object
      • urls String[] (optional) – An array of url corresponding to the resource whose generated code cache needs to be removed. If the list is empty then all entries in the cache directory will be removed.

    Returns Promise<void> – resolves when the code cache clear operation is complete.

    ses.setSpellCheckerEnabled(enable)

    • enable boolean

    Sets whether to enable the builtin spell checker.

    ses.isSpellCheckerEnabled()

    Returns boolean – Whether the builtin spell checker is enabled.

    ses.setSpellCheckerLanguages(languages)

    • languages string[] – An array of language codes to enable the spellchecker for.

    The built in spellchecker does not automatically detect what language a user is typing in. In order for the spell checker to correctly check their words you must call this API with an array of language codes. You can get the list of supported language codes with the ses.availableSpellCheckerLanguages property.

    Note: On macOS the OS spellchecker is used and will detect your language automatically. This API is a no-op on macOS.

    ses.getSpellCheckerLanguages()

    Returns string[] – An array of language codes the spellchecker is enabled for. If this list is empty the spellchecker will fallback to using en-US. By default on launch if this setting is an empty list Electron will try to populate this setting with the current OS locale. This setting is persisted across restarts.

    Note: On macOS the OS spellchecker is used and has its own list of languages. On macOS, this API will return whichever languages have been configured by the OS.

    ses.setSpellCheckerDictionaryDownloadURL(url)

    • url string – A base URL for Electron to download hunspell dictionaries from.

    By default Electron will download hunspell dictionaries from the Chromium CDN. If you want to override this behavior you can use this API to point the dictionary downloader at your own hosted version of the hunspell dictionaries. We publish a hunspell_dictionaries.zip file with each release which contains the files you need to host here.

    The file server must be case insensitive. If you cannot do this, you must upload each file twice: once with the case it has in the ZIP file and once with the filename as all lowercase.

    If the files present in hunspell_dictionaries.zip are available at https://example.com/dictionaries/language-code.bdic then you should call this api with ses.setSpellCheckerDictionaryDownloadURL('https://example.com/dictionaries/'). Please note the trailing slash. The URL to the dictionaries is formed as ${url}${filename}.

    Note: On macOS the OS spellchecker is used and therefore we do not download any dictionary files. This API is a no-op on macOS.

    ses.listWordsInSpellCheckerDictionary()

    Returns Promise<string[]> – An array of all words in app’s custom dictionary. Resolves when the full dictionary is loaded from disk.

    ses.addWordToSpellCheckerDictionary(word)

    • word string – The word you want to add to the dictionary

    Returns boolean – Whether the word was successfully written to the custom dictionary. This API will not work on non-persistent (in-memory) sessions.

    Note: On macOS and Windows 10 this word will be written to the OS custom dictionary as well

    ses.removeWordFromSpellCheckerDictionary(word)

    • word string – The word you want to remove from the dictionary

    Returns boolean – Whether the word was successfully removed from the custom dictionary. This API will not work on non-persistent (in-memory) sessions.

    Note: On macOS and Windows 10 this word will be removed from the OS custom dictionary as well

    ses.loadExtension(path[, options])

    • path string – Path to a directory containing an unpacked Chrome extension
    • options Object (optional)
      • allowFileAccess boolean – Whether to allow the extension to read local files over file:// protocol and inject content scripts into file:// pages. This is required e.g. for loading devtools extensions on file:// URLs. Defaults to false.

    Returns Promise<Extension> – resolves when the extension is loaded.

    This method will raise an exception if the extension could not be loaded. If there are warnings when installing the extension (e.g. if the extension requests an API that Electron does not support) then they will be logged to the console.

    Note that Electron does not support the full range of Chrome extensions APIs. See Supported Extensions APIs for more details on what is supported.

    Note that in previous versions of Electron, extensions that were loaded would be remembered for future runs of the application. This is no longer the case: loadExtension must be called on every boot of your app if you want the extension to be loaded.

    const { app, session } = require('electron')
    const path = require('node:path')

    app.whenReady().then(async () => {
    await session.defaultSession.loadExtension(
    path.join(__dirname, 'react-devtools'),
    // allowFileAccess is required to load the devtools extension on file:// URLs.
    { allowFileAccess: true }
    )
    // Note that in order to use the React DevTools extension, you'll need to
    // download and unzip a copy of the extension.
    })

    This API does not support loading packed (.crx) extensions.

    Note: This API cannot be called before the ready event of the app module is emitted.

    Note: Loading extensions into in-memory (non-persistent) sessions is not supported and will throw an error.

    ses.removeExtension(extensionId)

    • extensionId string – ID of extension to remove

    Unloads an extension.

    Note: This API cannot be called before the ready event of the app module is emitted.

    ses.getExtension(extensionId)

    • extensionId string – ID of extension to query

    Returns Extension | null – The loaded extension with the given ID.

    Note: This API cannot be called before the ready event of the app module is emitted.

    ses.getAllExtensions()

    Returns Extension[] – A list of all loaded extensions.

    Note: This API cannot be called before the ready event of the app module is emitted.

    ses.getStoragePath()

    Returns string | null – The absolute file system path where data for this session is persisted on disk. For in memory sessions this returns null.

    ses.clearData([options])

    • options Object (optional)
      • dataTypes String[] (optional) – The types of data to clear. By default, this will clear all types of data.
        • backgroundFetch – Background Fetch
        • cache – Cache
        • cookies – Cookies
        • downloads – Downloads
        • fileSystems – File Systems
        • indexedDB – IndexedDB
        • localStorage – Local Storage
        • serviceWorkers – Service Workers
        • webSQL – WebSQL
      • origins String[] (optional) – Clear data for only these origins. Cannot be used with excludeOrigins.
      • excludeOrigins String[] (optional) – Clear data for all origins except these ones. Cannot be used with origins.
      • avoidClosingConnections boolean (optional) – Skips deleting cookies that would close current network connections. (Default: false)
      • originMatchingMode String (optional) – The behavior for matching data to origins.
        • third-parties-included (default) – Storage is matched on origin in first-party contexts and top-level-site in third-party contexts.
        • origin-in-all-contexts – Storage is matched on origin only in all contexts.

    Returns Promise<void> – resolves when all data has been cleared.

    Clears various different types of data.

    This method clears more types of data and is more thourough than the clearStorageData method.

    Note: Cookies are stored at a broader scope than origins. When removing cookies and filtering by origins (or excludeOrigins), the cookies will be removed at the registrable domain level. For example, clearing cookies for the origin https://really.specific.origin.example.com/ will end up clearing all cookies for example.com. Clearing cookies for the origin https://my.website.example.co.uk/ will end up clearing all cookies for example.co.uk.

    For more information, refer to Chromium’s BrowsingDataRemover interface.

    Instance Properties

    The following properties are available on instances of Session:

    ses.availableSpellCheckerLanguages Readonly

    string[] array which consists of all the known available spell checker languages. Providing a language code to the setSpellCheckerLanguages API that isn’t in this array will result in an error.

    ses.spellCheckerEnabled

    boolean indicating whether builtin spell checker is enabled.

    ses.storagePath Readonly

    string | null indicating the absolute file system path where data for this session is persisted on disk. For in memory sessions this returns null.

    ses.cookies Readonly

    Cookies object for this session.

    ses.serviceWorkers Readonly

    ServiceWorkers object for this session.

    ses.webRequest Readonly

    WebRequest object for this session.

    ses.protocol Readonly

    Protocol object for this session.

    const { app, session } = require('electron')
    const path = require('node:path')

    app.whenReady().then(() => {
    const protocol = session.fromPartition('some-partition').protocol
    if (!protocol.registerFileProtocol('atom', (request, callback) => {
    const url = request.url.substr(7)
    callback({ path: path.normalize(path.join(__dirname, url)) })
    })) {
    console.error('Failed to register protocol')
    }
    })

    ses.netLog Readonly

    NetLog object for this session.

    const { app, session } = require('electron')

    app.whenReady().then(async () => {
    const netLog = session.fromPartition('some-partition').netLog
    netLog.startLogging('/path/to/net-log')
    // After some network events
    const path = await netLog.stopLogging()
    console.log('Net-logs written to', path)
    })
  • Screen

    Retrieve information about screen size, displays, cursor position, etc.

    Process: Main

    This module cannot be used until the ready event of the app module is emitted.

    screen is an EventEmitter.

    Note: In the renderer / DevTools, window.screen is a reserved DOM property, so writing let { screen } = require('electron') will not work.

    An example of creating a window that fills the whole screen:

    DOCS/FIDDLES/SCREEN/FIT-SCREEN (31.4.0)Open in Fiddle

    • main.js
    // Retrieve information about screen size, displays, cursor position, etc.
    //
    // For more info, see:
    // https://www.electronjs.org/docs/latest/api/screen

    const { app, BrowserWindow, screen } = require('electron/main')

    let mainWindow = null

    app.whenReady().then(() => {
    // Create a window that fills the screen's available work area.
    const primaryDisplay = screen.getPrimaryDisplay()
    const { width, height } = primaryDisplay.workAreaSize

    mainWindow = new BrowserWindow({ width, height })
    mainWindow.loadURL('https://electronjs.org')
    })

    Another example of creating a window in the external display:

    const { app, BrowserWindow, screen } = require('electron')

    let win

    app.whenReady().then(() => {
    const displays = screen.getAllDisplays()
    const externalDisplay = displays.find((display) => {
    return display.bounds.x !== 0 || display.bounds.y !== 0
    })

    if (externalDisplay) {
    win = new BrowserWindow({
    x: externalDisplay.bounds.x + 50,
    y: externalDisplay.bounds.y + 50
    })
    win.loadURL('https://github.com')
    }
    })

    Events

    The screen module emits the following events:

    Event: ‘display-added’

    Returns:

    Emitted when newDisplay has been added.

    Event: ‘display-removed’

    Returns:

    Emitted when oldDisplay has been removed.

    Event: ‘display-metrics-changed’

    Returns:

    • event Event
    • display Display
    • changedMetrics string[]

    Emitted when one or more metrics change in a display. The changedMetrics is an array of strings that describe the changes. Possible changes are boundsworkAreascaleFactor and rotation.

    Methods

    The screen module has the following methods:

    screen.getCursorScreenPoint()

    Returns Point

    The current absolute position of the mouse pointer.

    Note: The return value is a DIP point, not a screen physical point.

    screen.getPrimaryDisplay()

    Returns Display – The primary display.

    screen.getAllDisplays()

    Returns Display[] – An array of displays that are currently available.

    screen.getDisplayNearestPoint(point)

    Returns Display – The display nearest the specified point.

    screen.getDisplayMatching(rect)

    Returns Display – The display that most closely intersects the provided bounds.

    screen.screenToDipPoint(point) Windows

    Returns Point

    Converts a screen physical point to a screen DIP point. The DPI scale is performed relative to the display containing the physical point.

    screen.dipToScreenPoint(point) Windows

    Returns Point

    Converts a screen DIP point to a screen physical point. The DPI scale is performed relative to the display containing the DIP point.

    screen.screenToDipRect(window, rect) Windows

    Returns Rectangle

    Converts a screen physical rect to a screen DIP rect. The DPI scale is performed relative to the display nearest to window. If window is null, scaling will be performed to the display nearest to rect.

    screen.dipToScreenRect(window, rect) Windows

    Returns Rectangle

    Converts a screen DIP rect to a screen physical rect. The DPI scale is performed relative to the display nearest to window. If window is null, scaling will be performed to the display nearest to rect.

  • SafeStorage

    Allows access to simple encryption and decryption of strings for storage on the local machine.

    Process: Main

    This module adds extra protection to data being stored on disk by using OS-provided cryptography systems. Current security semantics for each platform are outlined below.

    • macOS: Encryption keys are stored for your app in Keychain Access in a way that prevents other applications from loading them without user override. Therefore, content is protected from other users and other apps running in the same userspace.
    • Windows: Encryption keys are generated via DPAPI. As per the Windows documentation: “Typically, only a user with the same logon credential as the user who encrypted the data can typically decrypt the data”. Therefore, content is protected from other users on the same machine, but not from other apps running in the same userspace.
    • Linux: Encryption keys are generated and stored in a secret store that varies depending on your window manager and system setup. Options currently supported are kwalletkwallet5kwallet6 and gnome-libsecret, but more may be available in future versions of Electron. As such, the security semantics of content protected via the safeStorage API vary between window managers and secret stores.
      • Note that not all Linux setups have an available secret store. If no secret store is available, items stored in using the safeStorage API will be unprotected as they are encrypted via hardcoded plaintext password. You can detect when this happens when safeStorage.getSelectedStorageBackend() returns basic_text.

    Note that on Mac, access to the system Keychain is required and these calls can block the current thread to collect user input. The same is true for Linux, if a password management tool is available.

    Methods

    The safeStorage module has the following methods:

    safeStorage.isEncryptionAvailable()

    Returns boolean – Whether encryption is available.

    On Linux, returns true if the app has emitted the ready event and the secret key is available. On MacOS, returns true if Keychain is available. On Windows, returns true once the app has emitted the ready event.

    safeStorage.encryptString(plainText)

    • plainText string

    Returns Buffer – An array of bytes representing the encrypted string.

    This function will throw an error if encryption fails.

    safeStorage.decryptString(encrypted)

    • encrypted Buffer

    Returns string – the decrypted string. Decrypts the encrypted buffer obtained with safeStorage.encryptString back into a string.

    This function will throw an error if decryption fails.

    safeStorage.setUsePlainTextEncryption(usePlainText)

    • usePlainText boolean

    This function on Linux will force the module to use an in memory password for creating symmetric key that is used for encrypt/decrypt functions when a valid OS password manager cannot be determined for the current active desktop environment. This function is a no-op on Windows and MacOS.

    safeStorage.getSelectedStorageBackend() Linux

    Returns string – User friendly name of the password manager selected on Linux.

    This function will return one of the following values:

    • basic_text – When the desktop environment is not recognised or if the following command line flag is provided --password-store="basic".
    • gnome_libsecret – When the desktop environment is X-CinnamonDeepinGNOMEPantheonXFCEUKUIunity or if the following command line flag is provided --password-store="gnome-libsecret".
    • kwallet – When the desktop session is kde4 or if the following command line flag is provided --password-store="kwallet".
    • kwallet5 – When the desktop session is kde5 or if the following command line flag is provided --password-store="kwallet5".
    • kwallet6 – When the desktop session is kde6.
    • unknown – When the function is called before app has emitted the ready event.
  • pushNotifications

    Process: Main

    Register for and receive notifications from remote push notification services

    For example, when registering for push notifications via Apple push notification services (APNS):

    const { pushNotifications, Notification } = require('electron')

    pushNotifications.registerForAPNSNotifications().then((token) => {
    // forward token to your remote notification server
    })

    pushNotifications.on('received-apns-notification', (event, userInfo) => {
    // generate a new Notification object with the relevant userInfo fields
    })

    Events

    The pushNotification module emits the following events:

    Event: ‘received-apns-notification’ macOS

    Returns:

    • event Event
    • userInfo Record<String, any>

    Emitted when the app receives a remote notification while running. See: https://developer.apple.com/documentation/appkit/nsapplicationdelegate/1428430-application?language=objc

    Methods

    The pushNotification module has the following methods:

    pushNotifications.registerForAPNSNotifications() macOS

    Returns Promise<string>

    Registers the app with Apple Push Notification service (APNS) to receive Badge, Sound, and Alert notifications. If registration is successful, the promise will be resolved with the APNS device token. Otherwise, the promise will be rejected with an error message. See: https://developer.apple.com/documentation/appkit/nsapplication/1428476-registerforremotenotificationtyp?language=objc

    pushNotifications.unregisterForAPNSNotifications() macOS

    Unregisters the app from notifications received from APNS. See: https://developer.apple.com/documentation/appkit/nsapplication/1428747-unregisterforremotenotifications?language=objc

  • protocol

    Register a custom protocol and intercept existing protocol requests.

    Process: Main

    An example of implementing a protocol that has the same effect as the file:// protocol:

    const { app, protocol, net } = require('electron')
    const path = require('node:path')
    const url = require('node:url')

    app.whenReady().then(() => {
    protocol.handle('atom', (request) => {
    const filePath = request.url.slice('atom://'.length)
    return net.fetch(url.pathToFileURL(path.join(__dirname, filePath)).toString())
    })
    })

    Note: All methods unless specified can only be used after the ready event of the app module gets emitted.

    Using protocol with a custom partition or session

    A protocol is registered to a specific Electron session object. If you don’t specify a session, then your protocol will be applied to the default session that Electron uses. However, if you define a partition or session on your browserWindow‘s webPreferences, then that window will use a different session and your custom protocol will not work if you just use electron.protocol.XXX.

    To have your custom protocol work in combination with a custom session, you need to register it to that session explicitly.

    const { app, BrowserWindow, net, protocol, session } = require('electron')
    const path = require('node:path')
    const url = require('url')

    app.whenReady().then(() => {
    const partition = 'persist:example'
    const ses = session.fromPartition(partition)

    ses.protocol.handle('atom', (request) => {
    const filePath = request.url.slice('atom://'.length)
    return net.fetch(url.pathToFileURL(path.resolve(__dirname, filePath)).toString())
    })

    const mainWindow = new BrowserWindow({ webPreferences: { partition } })
    })

    Methods

    The protocol module has the following methods:

    protocol.registerSchemesAsPrivileged(customSchemes)

    Note: This method can only be used before the ready event of the app module gets emitted and can be called only once.

    Registers the scheme as standard, secure, bypasses content security policy for resources, allows registering ServiceWorker, supports fetch API, streaming video/audio, and V8 code cache. Specify a privilege with the value of true to enable the capability.

    An example of registering a privileged scheme, that bypasses Content Security Policy:

    const { protocol } = require('electron')
    protocol.registerSchemesAsPrivileged([
    { scheme: 'foo', privileges: { bypassCSP: true } }
    ])

    A standard scheme adheres to what RFC 3986 calls generic URI syntax. For example http and https are standard schemes, while file is not.

    Registering a scheme as standard allows relative and absolute resources to be resolved correctly when served. Otherwise the scheme will behave like the file protocol, but without the ability to resolve relative URLs.

    For example when you load following page with custom protocol without registering it as standard scheme, the image will not be loaded because non-standard schemes can not recognize relative URLs:

    <body>
    <img src='test.png'>
    </body>

    Registering a scheme as standard will allow access to files through the FileSystem API. Otherwise the renderer will throw a security error for the scheme.

    By default web storage apis (localStorage, sessionStorage, webSQL, indexedDB, cookies) are disabled for non standard schemes. So in general if you want to register a custom protocol to replace the http protocol, you have to register it as a standard scheme.

    Protocols that use streams (http and stream protocols) should set stream: true. The <video> and <audio> HTML elements expect protocols to buffer their responses by default. The stream flag configures those elements to correctly expect streaming responses.

    protocol.handle(scheme, handler)

    • scheme string – scheme to handle, for example https or my-app. This is the bit before the : in a URL.
    • handler Function<GlobalResponse | Promise>

    Register a protocol handler for scheme. Requests made to URLs with this scheme will delegate to this handler to determine what response should be sent.

    Either a Response or a Promise<Response> can be returned.

    Example:

    const { app, net, protocol } = require('electron')
    const path = require('node:path')
    const { pathToFileURL } = require('url')

    protocol.registerSchemesAsPrivileged([
    {
    scheme: 'app',
    privileges: {
    standard: true,
    secure: true,
    supportFetchAPI: true
    }
    }
    ])

    app.whenReady().then(() => {
    protocol.handle('app', (req) => {
    const { host, pathname } = new URL(req.url)
    if (host === 'bundle') {
    if (pathname === '/') {
    return new Response('<h1>hello, world</h1>', {
    headers: { 'content-type': 'text/html' }
    })
    }
    // NB, this checks for paths that escape the bundle, e.g.
    // app://bundle/../../secret_file.txt
    const pathToServe = path.resolve(__dirname, pathname)
    const relativePath = path.relative(__dirname, pathToServe)
    const isSafe = relativePath && !relativePath.startsWith('..') && !path.isAbsolute(relativePath)
    if (!isSafe) {
    return new Response('bad', {
    status: 400,
    headers: { 'content-type': 'text/html' }
    })
    }

    return net.fetch(pathToFileURL(pathToServe).toString())
    } else if (host === 'api') {
    return net.fetch('https://api.my-server.com/' + pathname, {
    method: req.method,
    headers: req.headers,
    body: req.body
    })
    }
    })
    })

    See the MDN docs for Request and Response for more details.

    protocol.unhandle(scheme)

    • scheme string – scheme for which to remove the handler.

    Removes a protocol handler registered with protocol.handle.

    protocol.isProtocolHandled(scheme)

    • scheme string

    Returns boolean – Whether scheme is already handled.

    protocol.registerFileProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a file as the response. The handler will be called with request and callback where request is an incoming request for the scheme.

    To handle the request, the callback should be called with either the file’s path or an object that has a path property, e.g. callback(filePath) or callback({ path: filePath }). The filePath must be an absolute path.

    By default the scheme is treated like http:, which is parsed differently from protocols that follow the “generic URI syntax” like file:.

    protocol.registerBufferProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a Buffer as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a Buffer object or an object that has the data property.

    Example:

    protocol.registerBufferProtocol('atom', (request, callback) => {
    callback({ mimeType: 'text/html', data: Buffer.from('<h5>Response</h5>') })
    })

    protocol.registerStringProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a string as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a string or an object that has the data property.

    protocol.registerHttpProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send an HTTP request as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with an object that has the url property.

    protocol.registerStreamProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a stream as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a ReadableStream object or an object that has the data property.

    Example:

    const { protocol } = require('electron')
    const { PassThrough } = require('stream')

    function createStream (text) {
    const rv = new PassThrough() // PassThrough is also a Readable stream
    rv.push(text)
    rv.push(null)
    return rv
    }

    protocol.registerStreamProtocol('atom', (request, callback) => {
    callback({
    statusCode: 200,
    headers: {
    'content-type': 'text/html'
    },
    data: createStream('<h5>Response</h5>')
    })
    })

    It is possible to pass any object that implements the readable stream API (emits data/end/error events). For example, here’s how a file could be returned:

    protocol.registerStreamProtocol('atom', (request, callback) => {
    callback(fs.createReadStream('index.html'))
    })

    protocol.unregisterProtocol(scheme) Deprecated

    • scheme string

    Returns boolean – Whether the protocol was successfully unregistered

    Unregisters the custom protocol of scheme.

    protocol.isProtocolRegistered(scheme) Deprecated

    • scheme string

    Returns boolean – Whether scheme is already registered.

    protocol.interceptFileProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a file as a response.

    protocol.interceptStringProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a string as a response.

    protocol.interceptBufferProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a Buffer as a response.

    protocol.interceptHttpProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a new HTTP request as a response.

    protocol.interceptStreamProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Same as protocol.registerStreamProtocol, except that it replaces an existing protocol handler.

    protocol.uninterceptProtocol(scheme) Deprecated

    • scheme string

    Returns boolean – Whether the protocol was successfully unintercepted

    Remove the interceptor installed for scheme and restore its original handler.

    protocol.isProtocolIntercepted(scheme) Deprecated

    • scheme string

    Returns boolean – Whether scheme is already intercepted.

  • protocol

    Register a custom protocol and intercept existing protocol requests.

    Process: Main

    An example of implementing a protocol that has the same effect as the file:// protocol:

    const { app, protocol, net } = require('electron')
    const path = require('node:path')
    const url = require('node:url')

    app.whenReady().then(() => {
    protocol.handle('atom', (request) => {
    const filePath = request.url.slice('atom://'.length)
    return net.fetch(url.pathToFileURL(path.join(__dirname, filePath)).toString())
    })
    })

    Note: All methods unless specified can only be used after the ready event of the app module gets emitted.

    Using protocol with a custom partition or session

    A protocol is registered to a specific Electron session object. If you don’t specify a session, then your protocol will be applied to the default session that Electron uses. However, if you define a partition or session on your browserWindow‘s webPreferences, then that window will use a different session and your custom protocol will not work if you just use electron.protocol.XXX.

    To have your custom protocol work in combination with a custom session, you need to register it to that session explicitly.

    const { app, BrowserWindow, net, protocol, session } = require('electron')
    const path = require('node:path')
    const url = require('url')

    app.whenReady().then(() => {
    const partition = 'persist:example'
    const ses = session.fromPartition(partition)

    ses.protocol.handle('atom', (request) => {
    const filePath = request.url.slice('atom://'.length)
    return net.fetch(url.pathToFileURL(path.resolve(__dirname, filePath)).toString())
    })

    const mainWindow = new BrowserWindow({ webPreferences: { partition } })
    })

    Methods

    The protocol module has the following methods:

    protocol.registerSchemesAsPrivileged(customSchemes)

    Note: This method can only be used before the ready event of the app module gets emitted and can be called only once.

    Registers the scheme as standard, secure, bypasses content security policy for resources, allows registering ServiceWorker, supports fetch API, streaming video/audio, and V8 code cache. Specify a privilege with the value of true to enable the capability.

    An example of registering a privileged scheme, that bypasses Content Security Policy:

    const { protocol } = require('electron')
    protocol.registerSchemesAsPrivileged([
    { scheme: 'foo', privileges: { bypassCSP: true } }
    ])

    A standard scheme adheres to what RFC 3986 calls generic URI syntax. For example http and https are standard schemes, while file is not.

    Registering a scheme as standard allows relative and absolute resources to be resolved correctly when served. Otherwise the scheme will behave like the file protocol, but without the ability to resolve relative URLs.

    For example when you load following page with custom protocol without registering it as standard scheme, the image will not be loaded because non-standard schemes can not recognize relative URLs:

    <body>
    <img src='test.png'>
    </body>

    Registering a scheme as standard will allow access to files through the FileSystem API. Otherwise the renderer will throw a security error for the scheme.

    By default web storage apis (localStorage, sessionStorage, webSQL, indexedDB, cookies) are disabled for non standard schemes. So in general if you want to register a custom protocol to replace the http protocol, you have to register it as a standard scheme.

    Protocols that use streams (http and stream protocols) should set stream: true. The <video> and <audio> HTML elements expect protocols to buffer their responses by default. The stream flag configures those elements to correctly expect streaming responses.

    protocol.handle(scheme, handler)

    • scheme string – scheme to handle, for example https or my-app. This is the bit before the : in a URL.
    • handler Function<GlobalResponse | Promise>

    Register a protocol handler for scheme. Requests made to URLs with this scheme will delegate to this handler to determine what response should be sent.

    Either a Response or a Promise<Response> can be returned.

    Example:

    const { app, net, protocol } = require('electron')
    const path = require('node:path')
    const { pathToFileURL } = require('url')

    protocol.registerSchemesAsPrivileged([
    {
    scheme: 'app',
    privileges: {
    standard: true,
    secure: true,
    supportFetchAPI: true
    }
    }
    ])

    app.whenReady().then(() => {
    protocol.handle('app', (req) => {
    const { host, pathname } = new URL(req.url)
    if (host === 'bundle') {
    if (pathname === '/') {
    return new Response('<h1>hello, world</h1>', {
    headers: { 'content-type': 'text/html' }
    })
    }
    // NB, this checks for paths that escape the bundle, e.g.
    // app://bundle/../../secret_file.txt
    const pathToServe = path.resolve(__dirname, pathname)
    const relativePath = path.relative(__dirname, pathToServe)
    const isSafe = relativePath && !relativePath.startsWith('..') && !path.isAbsolute(relativePath)
    if (!isSafe) {
    return new Response('bad', {
    status: 400,
    headers: { 'content-type': 'text/html' }
    })
    }

    return net.fetch(pathToFileURL(pathToServe).toString())
    } else if (host === 'api') {
    return net.fetch('https://api.my-server.com/' + pathname, {
    method: req.method,
    headers: req.headers,
    body: req.body
    })
    }
    })
    })

    See the MDN docs for Request and Response for more details.

    protocol.unhandle(scheme)

    • scheme string – scheme for which to remove the handler.

    Removes a protocol handler registered with protocol.handle.

    protocol.isProtocolHandled(scheme)

    • scheme string

    Returns boolean – Whether scheme is already handled.

    protocol.registerFileProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a file as the response. The handler will be called with request and callback where request is an incoming request for the scheme.

    To handle the request, the callback should be called with either the file’s path or an object that has a path property, e.g. callback(filePath) or callback({ path: filePath }). The filePath must be an absolute path.

    By default the scheme is treated like http:, which is parsed differently from protocols that follow the “generic URI syntax” like file:.

    protocol.registerBufferProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a Buffer as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a Buffer object or an object that has the data property.

    Example:

    protocol.registerBufferProtocol('atom', (request, callback) => {
    callback({ mimeType: 'text/html', data: Buffer.from('<h5>Response</h5>') })
    })

    protocol.registerStringProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a string as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a string or an object that has the data property.

    protocol.registerHttpProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send an HTTP request as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with an object that has the url property.

    protocol.registerStreamProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully registered

    Registers a protocol of scheme that will send a stream as a response.

    The usage is the same with registerFileProtocol, except that the callback should be called with either a ReadableStream object or an object that has the data property.

    Example:

    const { protocol } = require('electron')
    const { PassThrough } = require('stream')

    function createStream (text) {
    const rv = new PassThrough() // PassThrough is also a Readable stream
    rv.push(text)
    rv.push(null)
    return rv
    }

    protocol.registerStreamProtocol('atom', (request, callback) => {
    callback({
    statusCode: 200,
    headers: {
    'content-type': 'text/html'
    },
    data: createStream('<h5>Response</h5>')
    })
    })

    It is possible to pass any object that implements the readable stream API (emits data/end/error events). For example, here’s how a file could be returned:

    protocol.registerStreamProtocol('atom', (request, callback) => {
    callback(fs.createReadStream('index.html'))
    })

    protocol.unregisterProtocol(scheme) Deprecated

    • scheme string

    Returns boolean – Whether the protocol was successfully unregistered

    Unregisters the custom protocol of scheme.

    protocol.isProtocolRegistered(scheme) Deprecated

    • scheme string

    Returns boolean – Whether scheme is already registered.

    protocol.interceptFileProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a file as a response.

    protocol.interceptStringProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a string as a response.

    protocol.interceptBufferProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a Buffer as a response.

    protocol.interceptHttpProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Intercepts scheme protocol and uses handler as the protocol’s new handler which sends a new HTTP request as a response.

    protocol.interceptStreamProtocol(scheme, handler) Deprecated

    Returns boolean – Whether the protocol was successfully intercepted

    Same as protocol.registerStreamProtocol, except that it replaces an existing protocol handler.

    protocol.uninterceptProtocol(scheme) Deprecated

    • scheme string

    Returns boolean – Whether the protocol was successfully unintercepted

    Remove the interceptor installed for scheme and restore its original handler.

    protocol.isProtocolIntercepted(scheme) Deprecated

    • scheme string

    Returns boolean – Whether scheme is already intercepted.

  • process

    Extensions to process object.

    Process: MainRenderer

    Electron’s process object is extended from the Node.js process object. It adds the following events, properties, and methods:

    Sandbox

    In sandboxed renderers the process object contains only a subset of the APIs:

    • crash()
    • hang()
    • getCreationTime()
    • getHeapStatistics()
    • getBlinkMemoryInfo()
    • getProcessMemoryInfo()
    • getSystemMemoryInfo()
    • getSystemVersion()
    • getCPUUsage()
    • uptime()
    • argv
    • execPath
    • env
    • pid
    • arch
    • platform
    • sandboxed
    • contextIsolated
    • type
    • version
    • versions
    • mas
    • windowsStore
    • contextId

    Events

    Event: ‘loaded’

    Emitted when Electron has loaded its internal initialization script and is beginning to load the web page or the main script.

    Properties

    process.defaultApp Readonly

    boolean. When the app is started by being passed as parameter to the default Electron executable, this property is true in the main process, otherwise it is undefined. For example when running the app with electron ., it is true, even if the app is packaged (isPackaged) is true. This can be useful to determine how many arguments will need to be sliced off from process.argv.

    process.isMainFrame Readonly

    booleantrue when the current renderer context is the “main” renderer frame. If you want the ID of the current frame you should use webFrame.routingId.

    process.mas Readonly

    boolean. For Mac App Store build, this property is true, for other builds it is undefined.

    process.noAsar

    boolean that controls ASAR support inside your application. Setting this to true will disable the support for asar archives in Node’s built-in modules.

    process.noDeprecation

    boolean that controls whether or not deprecation warnings are printed to stderr. Setting this to true will silence deprecation warnings. This property is used instead of the --no-deprecation command line flag.

    process.resourcesPath Readonly

    string representing the path to the resources directory.

    process.sandboxed Readonly

    boolean. When the renderer process is sandboxed, this property is true, otherwise it is undefined.

    process.contextIsolated Readonly

    boolean that indicates whether the current renderer context has contextIsolation enabled. It is undefined in the main process.

    process.throwDeprecation

    boolean that controls whether or not deprecation warnings will be thrown as exceptions. Setting this to true will throw errors for deprecations. This property is used instead of the --throw-deprecation command line flag.

    process.traceDeprecation

    boolean that controls whether or not deprecations printed to stderr include their stack trace. Setting this to true will print stack traces for deprecations. This property is instead of the --trace-deprecation command line flag.

    process.traceProcessWarnings

    boolean that controls whether or not process warnings printed to stderr include their stack trace. Setting this to true will print stack traces for process warnings (including deprecations). This property is instead of the --trace-warnings command line flag.

    process.type Readonly

    string representing the current process’s type, can be:

    • browser – The main process
    • renderer – A renderer process
    • worker – In a web worker
    • utility – In a node process launched as a service

    process.versions.chrome Readonly

    string representing Chrome’s version string.

    process.versions.electron Readonly

    string representing Electron’s version string.

    process.windowsStore Readonly

    boolean. If the app is running as a Windows Store app (appx), this property is true, for otherwise it is undefined.

    process.contextId Readonly

    string (optional) representing a globally unique ID of the current JavaScript context. Each frame has its own JavaScript context. When contextIsolation is enabled, the isolated world also has a separate JavaScript context. This property is only available in the renderer process.

    process.parentPort

    Electron.ParentPort property if this is a UtilityProcess (or null otherwise) allowing communication with the parent process.

    Methods

    The process object has the following methods:

    process.crash()

    Causes the main thread of the current process crash.

    process.getCreationTime()

    Returns number | null – The number of milliseconds since epoch, or null if the information is unavailable

    Indicates the creation time of the application. The time is represented as number of milliseconds since epoch. It returns null if it is unable to get the process creation time.

    process.getCPUUsage()

    Returns CPUUsage

    process.getHeapStatistics()

    Returns Object:

    • totalHeapSize Integer
    • totalHeapSizeExecutable Integer
    • totalPhysicalSize Integer
    • totalAvailableSize Integer
    • usedHeapSize Integer
    • heapSizeLimit Integer
    • mallocedMemory Integer
    • peakMallocedMemory Integer
    • doesZapGarbage boolean

    Returns an object with V8 heap statistics. Note that all statistics are reported in Kilobytes.

    process.getBlinkMemoryInfo()

    Returns Object:

    • allocated Integer – Size of all allocated objects in Kilobytes.
    • total Integer – Total allocated space in Kilobytes.

    Returns an object with Blink memory information. It can be useful for debugging rendering / DOM related memory issues. Note that all values are reported in Kilobytes.

    process.getProcessMemoryInfo()

    Returns Promise<ProcessMemoryInfo> – Resolves with a ProcessMemoryInfo

    Returns an object giving memory usage statistics about the current process. Note that all statistics are reported in Kilobytes. This api should be called after app ready.

    Chromium does not provide residentSet value for macOS. This is because macOS performs in-memory compression of pages that haven’t been recently used. As a result the resident set size value is not what one would expect. private memory is more representative of the actual pre-compression memory usage of the process on macOS.

    process.getSystemMemoryInfo()

    Returns Object:

    • total Integer – The total amount of physical memory in Kilobytes available to the system.
    • free Integer – The total amount of memory not being used by applications or disk cache.
    • swapTotal Integer Windows Linux – The total amount of swap memory in Kilobytes available to the system.
    • swapFree Integer Windows Linux – The free amount of swap memory in Kilobytes available to the system.

    Returns an object giving memory usage statistics about the entire system. Note that all statistics are reported in Kilobytes.

    process.getSystemVersion()

    Returns string – The version of the host operating system.

    Example:

    const version = process.getSystemVersion()
    console.log(version)
    // On macOS -> '10.13.6'
    // On Windows -> '10.0.17763'
    // On Linux -> '4.15.0-45-generic'

    Note: It returns the actual operating system version instead of kernel version on macOS unlike os.release().

    process.takeHeapSnapshot(filePath)

    • filePath string – Path to the output file.

    Returns boolean – Indicates whether the snapshot has been created successfully.

    Takes a V8 heap snapshot and saves it to filePath.

    process.hang()

    Causes the main thread of the current process hang.

    process.setFdLimit(maxDescriptors) macOS Linux

    • maxDescriptors Integer

    Sets the file descriptor soft limit to maxDescriptors or the OS hard limit, whichever is lower for the current process.