electron-quick-start VS node-addon-api

"pack": "build --dir","dist": "build","electron": "electron main.js","postinstall": "install-app-deps" Create main.js I just copied the code from the electron quick start. The only change I make is to the location of index.html which I set to /dist/index.html

Tauri has a small footprint by default but what about when we pack NodeJS binary with our app? The result of this is surprising. Taurine app is 3 times smaller than electron app. Compiled the Tauri app in .app the format has 63MB and the electron app in the same format has 205MB.

I cloned the quick-start directory from Electron's github and spun up my node-js. No problems there. 🦾

Well it automatically downloads electron 19.0.4 from git clone https://github.com/electron/electron-quick-start. Then I instantly receive the vulnerability issues from npm install & npm start. Not sure why the packages aren't upgrading to newest on install

# Clone this repository git clone https://github.com/electron/electron-quick-start # Go into the repository cd electron-quick-start # Install dependencies npm install # Run the app npm start

This was like one of the top results when I googled for like "electron stuck npm" https://github.com/electron/electron-quick-start/issues/127

This question already has answers here: How to deploy an Electron app as an executable or installable in Windows? (10 answers) Closed 2 years ago.I've been learning how to create applications in Electron and I need help compiling a simple project to a Windows executable. The program is a clone from this Github repo: https://github.com/electron/electron-quick-start. On the repo readme it shows how to run the program:

Create an electron application. Follow the steps here: https://github.com/electron/electron-quick-start

In any event, I just took a closer look at my project, and it looks like the key thing is to wait for Electron's ready event before registering the ipcMain listeners. So, taking Electron's quick-start example as a starting point, you would want to do it in the app.whenReady().then(() => { ... }) callback, probably just before creating the window. Does that help?

We will first initialise an empty electron project that will look similar to an electron first app or electron quick starter repository

It's the official extension mechanism, and therefore has the best support

If we want it fast, Node-API looks like a perfect solution. A library written in C/C++ must be fast. If you prefer to use C++ over C, the node-addon-api can help. This is probably one of the best solutions available, especially since it is officially supported by the Node.js team. It’s super stable once it is built, but it can be painful during development. Errors are often far from easy to understand, so if you are no expert in C, it might kick your ass very easily.

The Node-API Team proudly announces the release of version 7.0.0 of node-addon-api, the C++ wrapper of the ABI-stable C-based Node-API (npm, GitHub).

Node ffi is an unnecessary wrapper around addon api. See https://github.com/nodejs/node-addon-api

Did a little digging, napi is header file in an npm package that's supposed to help you build C++ addons, node_api is node's actual API. https://github.com/nodejs/node-addon-api you might have already been using this. The examples have enough code that it shouldn't be too bad to get started