Control application configuration and behavior without changing code.
Certain Electron behaviors are controlled by environment variables because they are initialized earlier than the command line flags and the app's code.
POSIX shell example:
$ export ELECTRON_ENABLE_LOGGING=true
$ electronWindows console example:
> set ELECTRON_ENABLE_LOGGING=true
> electronThe following environment variables are intended primarily for use at runtime in packaged Electron applications.
Electron includes support for a subset of Node's NODE_OPTIONS. The majority are supported with the exception of those which conflict with Chromium's use of BoringSSL.
Example:
export NODE_OPTIONS="--no-warnings --max-old-space-size=2048"Unsupported options are:
--use-bundled-ca
--force-fips
--enable-fips
--openssl-config
--use-openssl-caNODE_OPTIONS are explicitly disallowed in packaged apps.
You can provide an API key for making requests to Google's geocoding webservice. To do this, place the following code in your main process file, before opening any browser windows that will make geocoding requests:
process.env.GOOGLE_API_KEY = 'YOUR_KEY_HERE'For instructions on how to acquire a Google API key, visit this page. By default, a newly generated Google API key may not be allowed to make geocoding requests. To enable geocoding requests, visit this page.
Disables ASAR support. This variable is only supported in forked child processes
and spawned child processes that set ELECTRON_RUN_AS_NODE.
Starts the process as a normal Node.js process.
Don't attach to the current console session.
Don't use the global menu bar on Linux.
Set the trash implementation on Linux. Default is gio.
Options:
gvfs-trashtrash-clikioclient5kioclient
The following environment variables are intended primarily for development and debugging purposes.
Prints Chrome's internal logging to the console.
When Electron reads from an ASAR file, log the read offset and file path to
the system tmpdir. The resulting file can be provided to the ASAR module
to optimize file ordering.
Prints the stack trace to the console when Electron crashes.
This environment variable will not work if the crashReporter is started.
Shows the Windows's crash dialog when Electron crashes.
This environment variable will not work if the crashReporter is started.
When running from the electron package, this variable tells
the electron command to use the specified build of Electron instead of
the one downloaded by npm install. Usage:
export ELECTRON_OVERRIDE_DIST_PATH=/Users/username/projects/electron/out/Debug