leveldown | An abstract-leveldown compliant store | Runtime Evironment library

The above link indeed worked for me. I was using Node V17 (odd number) and have now switched to V16 and all working well now.

You have to install Visual Studio Community 2022 as well as Visual Studio Code. And when installing Visual Studio Community, you have to install desktop development with C++ with some optional packages.

As per the electron-builder CLI documentation, all platform switches accept a "target list", which in essence is what you configure in your package.json with your different platform entries (build..target, e.g. build.linux.target).

However, by using these target lists, you can specify which targets you want to build and exclude all others. Since Linux' switch is the last in the switch list -ml, Electron Builder interprets this as though you want to pass it a target list. This does not apply to the macOS build step because then you would have to use -m -l , -ml apparently only applies to Linux.

Thus, by appending build to the command line, you tell Electron Builder to compile all configured targets for macOS but only build the Linux target called build. Since there is no such target, Electron Builder crashes. Removing build from your command will do the trick.

The solution is actually very simple, all you need to do is to set --target= again when you do nw-gyp build, like this:

You have installed Python 3 but you are running code that expects Python 2. You can install the python2 package and then you may be able to instruct your npm install process to use /usr/bin/python2 instead of /usr/bin/python.

If that's not possible, you should be able to symlink /usr/bin/python to /usr/bin/python2. By default, CentOS 8 doesn't have a /usr/bin/python (it has only python2 or python3 commands), so this should be harmless.

Note that Python 2 has just reached end of life. Any software that still expects Python 2 at this point may not have seen updates in a while.