Comma Chameleon has a gh-pages served site in its docs folder that we
are going to ignore for now

-_____-)

Exec *is* required in order that the build package terminates

other electron applications adhere to const instead of globals,
commonly declaring a group of them together like so `const {Menu, app,
BrowserWindow, dialog} = require('electron')
`

This is a HACK and will not persist in the long run, its technically
abusing a feature of (standard
js)[https://www.npmjs.com/package/standard#i-use-a-library-that-pollutes
-the-global-namespace-how-do-i-prevent-variable-is-not-defined-errors].
Doing so is warranted as adhering to standard JS will involve a
refactor of code logic which I deem better addressed in its own ticket

This is a noted problem in the standard documentation relating to how
mocha works as a test suite

basically catching jQuery and the HandsOnTable object

StandardJS mandates path.join but Electron stipulation of interpolation
also passes muster
https://github.com/electron/electron/blob/master/docs/api/browser-window
.md

Standard requires errors to be thrown

this seems a suspect/shallow way of catching errors, but the usual way
of `.on(err, //etc)` doesn’t satisfy standards so including this way to
satisfy standardJS

Including only to satisfy StandardJS - I’m really not sure that errors
need to be caught during specs but happy to be corrected by someone
more au fait with this

this may or may not be worth keeping

let statement declares a block scope local variable, which can then be
modified in mocha `beforeEach` and still pass standardJS standards

There were two vars called hot up until this point
I suspect this spec (line 25 - 35) needs a refactor

not sure if this will work but making the amendment so this PR is
consistent all the way around