Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Electron 11: Methods on `remote.screen` are not defined
See original GitHub issueNote: Spectron currently depends on the remote module, and will need to be rewritten not to depend on remote to match Electron’s main repo. We’re currently looking for help from folks who may be interested in helping with this initiative - if you might be interested, please let us know!
Beginning in Electron 11, the screen module in both the main process and the remote module is now exported as a proxy, which lazily calls createScreen on first access. This proxy does not seem to be loading properly in the remote module, and is causing an error with remote’s screen API methods.
This is a known issue within remote only; calling screen methods from the main process works as expected.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My fix for the
remote.screenissue was backported in Electron 11.0.3, just released.@deanylev Just triaged your bug in the electron/electron repo, we’ll see if we can add a fix