Run electron-forge on the Linux Subsystem for Windows (WSL)

electron-forge does not work on the WSL by default. This is expected since WSL can’t run GUI applications on linux. When using “vanilla” electron through the WSL manually installing the win32 version of electron fixes this issue. (see here) Unfortunatly, this approach results in this error when using electron-forge

(electron:325): Gtk-WARNING **: cannot open display:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test@1.0.0 start: `electron-forge start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

It seems like the reinstalling of electron had no effect - even though im unsure why this is happening.

Instructions to reproduce:

• Install the Debian WSL
• Install electron-forge in wsl
• electron-forge init test ; cd test
• npm install && npm uninstall electron && export npm_config_platform=win32 && npm install electron && unset npm_config_platform
• npm start

[malept]

I’ve talked to some Electron devs who are more familiar with the Windows environment than I am, and the consensus is that you should be using WSL + Forge just to package for Linux (i.e., .deb, .rpm, Snap). For the development cycle, you should be using Windows proper (e.g., CMD/Powershell for CLI).

[malept]

As Paul said, you’ll need an X server running if you want to run an Electron app under WSL without a lot of headaches (which uses the Linux target, because you’re technically running under Linux).

Feel free to try to figure out how to get a Forge project with a Windows target working (I would suggest using the v6 beta instead of v5, if only because we’re not adding any new features to v5), and if it ends up being a relatively clean solution (unlike that fourth bullet point in your repro instructions), you should definitely file an issue/PR in the appropriate project.