Actually, it just appears to be the most reliable way to embed both Node.js and Chromium web browser for the client.
The best way (and most secure way) to use it, is via inter-process communication (ipcMain / ipcRender), which can also be done in pure Node.js (i.e. no Electron, is also true threading). However, I still prefer to do it the web server way.
Actually, if you don't really need the Node.js part, or you want different backends, there are many alternatives, e.g. Neutralino.js, zserge/webview. There is no guarantee that Chromium / CEF will work the way you wanted, though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Combination of my laziness and maintainability. My current stack is
They all may change at any time, though.
Building a highly customizable quiz app, with embedded dictionaries, that can work on mobile, and sync to desktop.
How are you finding Electron I am yet to create anything with it but I hear that it is quite easy to learn?
Actually, it just appears to be the most reliable way to embed both Node.js and Chromium web browser for the client.
The best way (and most secure way) to use it, is via inter-process communication (ipcMain / ipcRender), which can also be done in pure Node.js (i.e. no Electron, is also true threading). However, I still prefer to do it the web server way.
Actually, if you don't really need the Node.js part, or you want different backends, there are many alternatives, e.g. Neutralino.js, zserge/webview. There is no guarantee that Chromium / CEF will work the way you wanted, though.