react-electron | Boilerplate for creating an Electron desktop app | Frontend Framework library

By default, Electron Builder compiles your application and packs all resources into one large archive file (think of it as a ZIP file) which can be read just fine because Electron brings support for this format known as "ASAR".

When running the built program, the code will be read from the archive. This means that __dirname will point to a directory inside the archive. The operating system, however, cannot read from the archive. Since you did not actually include the piece of code calling child_process.spawn (), I can only speculate on why you get ENOTDIR, which hints that a given path is not a directory when it was expected to be one, but I assume this is because you point to a path inside the ASAR file.

When relying on external binaries, it is a good idea to keep them outside the ASAR archive and programmatically find the path to them (which is quite complex) or by preventing Electron Builder from compiling your app into an ASAR file. However, you would also have to ask Electron Builder to include the executable in the built version of your app. This can be done by modifying your package.json:

ipcRenderer is the module you should, and do, use in the renderer process (either scripts attached to HTML pages if there is no contextIsolation, or preload otherwise).

The module to use in the main process is called ipcMain.

Yes it's possible according to electron docs. options for window

alwaysOnTop Boolean (optional) - Whether the window should always stay on top of other windows. Default is false.

more info Electron Window

Update I solved my problem, partly thanks to mu-majid in the comments. Here is the updated code in case anyone is starting out and stumbles across this.

The issue is you provide an empty string as initial state. The first console log is from the render function and the second is from this.renderTableHeader. The problem happens when you hit this line: let header = Object.keys(this.state.Products[0])

I got the answer for this case. In posted situation, I used nodeIntegration: true then I implemented the example used const remote = window.require('electron').remote and remote.require features. Then, AddressForArgs(†1) via ref.HexAddress returns electron client based address maybe ( I don't know more internals of the node-ref-napi, node-ffi-napi and electron just now ).

Therefore, I tried change to nodeIntegration: false setting with preload features.

You can achive your idea by using ipc at Electron. I posted an answer before. Please check the below.

how to communicate between react and electron

But here is the pre-requirements.

You should enable the nodeintegration when you are creating the BrowserWindow So at your code, it should be like this

Just create a react videoCall Component then create a window and load a url with query params like this,