Fix debug calls while in a preload script inside Electron

[MarshallOfSound]

In electron preload scripts document.documentElement is null, this is quite a simple fix that simply checks for a good value 👍

[thebigredgeek]

wondering if you meant to add an && to the end of the null pointer check document.documentElement? This looks like a syntax error

[MarshallOfSound]

Idek where that && went, let's pretend this didn't happen and move on 😆

[thebigredgeek]

Pretty sure there is a syntax error here. I added linting to browser.js on master, but I don't think it ran on this PR.

[anaisbetts]

This is a dupe of #368, no?

[MarshallOfSound]

@paulcbetts Hmmm, maybe I got a module before that patch or someone hasn't updated their entire dependency tree. I'll wipe node-modules try again 👍

[graysonlang]

Just a heads up: If you want this to not error out in the context of Electron's main process (which it did in earlier versions), you will also need to check for typeof navigator !== 'undefined' on lines 56 and 58.

[thebigredgeek]

@MarshallOfSound conflicts :(

[anaisbetts]

Just a heads up: If you want this to not error out in the context of Electron's main process (which it did in earlier versions), you will also need to check for typeof navigator !== 'undefined' on lines 56 and 58.

In the main process we shouldn't ever get to browser.js because we will have been redirected to use the node version, peep #324

[MarshallOfSound]

Resetting yarn cache finally pulled in a good version of this module 👍 @paulcbetts fix works fine