1.3 KiB
Environment Variables
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
ELECTRON_RUN_AS_NODE
Starts the process as a normal Node.js process.
ELECTRON_ENABLE_LOGGING
Prints Chrome's internal logging to the console.
ELECTRON_LOG_ASAR_READS
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.
ELECTRON_ENABLE_STACK_DUMPING
Prints the stack trace to the console when Electron crashes.
This environment variable will not work if the crashReporter is started.
ELECTRON_DEFAULT_ERROR_MODE Windows
Shows the Windows's crash dialog when Electron crashes.
This environment variable will not work if the crashReporter is started.
ELECTRON_NO_ATTACH_CONSOLE Windows
Don't attach to the current console session.
ELECTRON_FORCE_WINDOW_MENU_BAR Linux
Don't use the global menu bar on Linux.