2018-01-26 08:29:15 +03:00
|
|
|
# Support for Electron Forge
|
|
|
|
|
|
2019-06-10 17:58:58 +03:00
|
|
|
If you have questions about usage, we encourage you to browse the [website](https://www.electronforge.io/),
|
2018-01-26 08:29:15 +03:00
|
|
|
and visit one of the several [community-driven sites](https://github.com/electron/electron#community).
|
|
|
|
|
|
|
|
|
|
## Troubleshooting
|
|
|
|
|
|
|
|
|
|
One way to troubleshoot potential problems is to set the `DEBUG` environment variable before
|
|
|
|
|
running `electron-forge`. This will print debug information from the specified modules. The
|
|
|
|
|
value of the environment variable is a comma-separated list of modules which support this logging
|
|
|
|
|
feature. Known modules include:
|
|
|
|
|
|
|
|
|
|
* `electron-download`
|
|
|
|
|
* `electron-forge:*` (always use this one before filing an issue)
|
|
|
|
|
* `electron-installer-debian`
|
|
|
|
|
* `electron-installer-dmg`
|
|
|
|
|
* `electron-installer-flatpak`
|
|
|
|
|
* `electron-installer-redhat`
|
2017-09-26 21:06:51 +03:00
|
|
|
* `electron-installer-snap:*`
|
2018-01-26 08:29:15 +03:00
|
|
|
* `electron-osx-sign`
|
|
|
|
|
* `electron-packager`
|
|
|
|
|
* `electron-rebuild`
|
|
|
|
|
* `electron-windows-installer:main`
|
|
|
|
|
* `electron-windows-store`
|
|
|
|
|
* `extract-zip`
|
|
|
|
|
* `get-package-info`
|
|
|
|
|
|
|
|
|
|
We use the [`debug`](https://www.npmjs.com/package/debug#usage) module for this functionality. It
|
|
|
|
|
has examples on how to set environment variables if you don't know how.
|
|
|
|
|
|
|
|
|
|
**If you are using `npm run` to execute `electron-forge`, run the `electron-forge` command
|
|
|
|
|
without using `npm run` and make a note of the output, because `npm run` does not print out error
|
|
|
|
|
messages when a script errors.**
|
