@alfreddagenais thank you for this patch, it helps resolve the issue locally. Expanding upon this, according to this stackoverflow issue, the electron.remote is only available if call(s) to new BrowserWindow are extended with the following parmeter:

const myWindow = new BrowserWindow({ webPreferences: { enableRemoteModule: true } });

I confirmed this locally, if I modify my application such that the main window is created w/ this parameter the error disappears, no hotfix is needed.

The issue is that many will not be able to enable the remote module (it entails security implications and is against electron security guidelines.

Your hotfix works as an interim solution for the time being but does entail various side-effects, namely various BrowserWindow and WebContents methods will not be available in the spectron API and perhaps more importantly the spectron Application 'stop' method will not actually stop the application. In the original (premodified) implementation, the stop method delegates to electron.remote.app.quit which actually quits the application but in your patch, this is stubbed out and the resolve/reject methods are manually called.

All in all great addition, though others should be aware of the tradeoffs until we figure out a solution that works in all cases (ideally spectron should not depend on the remote module, but not sure if this is possible)

@movitto I was about to go crazy thank you for your comment!