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
$ electron
Windows console example:
> set ELECTRON_ENABLE_LOGGING=true
> electron
The following environment variables are intended primarily for use at runtime in packaged Electron applications.
Electron includes a hardcoded API key for making requests to Google's geocoding webservice. Because this API key is included in every version of Electron, it often exceeds its usage quota. To work around this, you can supply your own Google API key in the environment. 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
.
The following environment variables are intended primarily for development and debugging purposes.
Starts the process as a normal Node.js process.
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.
Don't attach to the current console session.
Don't use the global menu bar on Linux.