Upgrade Electron to latest version

[magne4000]

Many bugs that are occurring are due to the outdated Electron version used.
Unfortunately upgrading Electron as always be a major difficulty on this project, and this time its still no luck as much work needs to be done to be able to upgrade to the latest version (or even just from v7 to v9).

Persistence layer

Context: What we learned from data persistence in our growing Electron app

sqlite3 package will not be able to be loaded inside Electron renderer process. All core logic is currently handled in a "worker" process, which is just a frameless renderer process. Persistence is a part of this.

We cannot easily replace the package with better-sqlite3 as its not compatible with sequelize. And we are not sure if it would completely work.

Best bet would be to get rid of sqlite and sequelize and use IndexedDb, as we are in a renderer process (at the time we wrote the article, the persistence was done in the main process).

BrowserWindow extension APIs

See https://www.electronjs.org/docs/breaking-changes#deprecated-browserwindow-extension-apis
Not sure if this will be a no brainer, but my guess is that it will probably not be as simple as the documentation suggests.

Deprecation of worldSafeExecuteJavaScript

See https://www.electronjs.org/docs/breaking-changes#default-changed-worldsafeexecutejavascript-defaults-to-true
It will probably have an impact, but its unknown yet.

Other minor changes

All (most?) of breaking changes are listed here https://www.electronjs.org/docs/breaking-changes. Things like changes in API names shouldn't be too difficult to migrate.

Of course, any other/better idea is welcome on the subject!

[Virgus]

Hello magne4000, I'm sorry I'm not skilled enough to be of some help, but just to mention a detail that might be of some help:
the electron version used in Canary version, despite is almost 18 months old, is working fine with everything I used so far.
https://github.com/getstation/station-canary/releases/tag/0.19.131