| 1 | # Support for Electron Forge
|
| 2 |
|
| 3 | If you have questions about usage, we encourage you to browse the [website](https://electronforge.io/),
|
| 4 | and visit one of the several [community-driven sites](https://github.com/electron/electron#community).
|
| 5 |
|
| 6 | ## Troubleshooting
|
| 7 |
|
| 8 | One way to troubleshoot potential problems is to set the `DEBUG` environment variable before
|
| 9 | running `electron-forge`. This will print debug information from the specified modules. The
|
| 10 | value of the environment variable is a comma-separated list of modules which support this logging
|
| 11 | feature. Known modules include:
|
| 12 |
|
| 13 | * `electron-compile:*`
|
| 14 | * `electron-download`
|
| 15 | * `electron-forge:*` (always use this one before filing an issue)
|
| 16 | * `electron-installer-debian`
|
| 17 | * `electron-installer-dmg`
|
| 18 | * `electron-installer-flatpak`
|
| 19 | * `electron-installer-redhat`
|
| 20 | * `electron-installer-snap:*`
|
| 21 | * `electron-osx-sign`
|
| 22 | * `electron-packager`
|
| 23 | * `electron-rebuild`
|
| 24 | * `electron-windows-installer:main`
|
| 25 | * `electron-windows-store`
|
| 26 | * `extract-zip`
|
| 27 | * `get-package-info`
|
| 28 |
|
| 29 | We use the [`debug`](https://www.npmjs.com/package/debug#usage) module for this functionality. It
|
| 30 | has examples on how to set environment variables if you don't know how.
|
| 31 |
|
| 32 | **If you are using `npm run` to execute `electron-forge`, run the `electron-forge` command
|
| 33 | without using `npm run` and make a note of the output, because `npm run` does not print out error
|
| 34 | messages when a script errors.**
|