tutorial-app | minimum working example of a web application | Continous Integration 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:

By using the --asar switch in your package-win script, you're telling Electron Packager to write all your app's sources, including any directories, into an Asar archive. This is a TAR-like archive file located under resources/app.asar in your build directory (in your case, the complete path will be release-builds//resources/app.asar). Your app will run off of that just fine, because Electron handles loading files from the archive for you.

However, as this is an archive, you cannot simply write files to it, and it seems that you're constructing the path to your /saves/ directory yourself and not using __dirname, which would point to the Asar archive.

That being said, one possible workaround is to either not use Asar at all (by removing the --asar switch from your package-win script), which will leave your app's sources pretty much unprotected from curious eyes, or by checking if the saves/ directory exists and create it if not upon app startup, which seems like the way to go.

To do so, add the following code anywhere in your main process' file, in your case main.js (I recommend putting this code near the top):

I'm answering this question myself because I was able to package it

Firstly, I used "electron-builder": "^22.9.1", instead of electron-packager.

Next, the reason it wasn't being packaged is because the storage location of my app data wasn't specified properly.

I was using sqlite database and a json file.

On windows you have make sure it gets saved under APP DATA > your foldername. Electron will handle this automatically if you use

Yes, writing to the application location is not a good idea and often forbidden. It should be sufficient to use the appdata folder which is usually used for application settings etc.

app.getPath(name) is the function you are looking for.

Then do something like:

I don't know if this will help but what I do is to build an absolute path using the path library (actually I use upath for cross platform compatibility because I often need to save the path to a file).

Solution:

Move the "xmlbuilder": "^15.1.1" line to be inside the "dependencies"

Here is the updated package.json file

After couple of frustrating hours goggling for answers and trying different approaches, I figured it was not the problem with my code but rather problem while bootstrapping with create-react-app using node version v8.0.0.

So I deleted the entire project and followed below steps which solved my issue -

1. Deleted the entire project. Since I had not written much code so far, So I simply did that. If you have already written a lot of code ,please take a backup.
2. I installed NVM(Node Version Manager).I used this link How to install NVM in Ubuntu to install the same.
3. Once nvm is installed use nvm install 12.0.0(or the node version > 8.0.0 which you would like to use). This was actually the issue for me. For create-react-app to bootstrap successfully you should use node version > 8.0.0.
4. After this I use nvm use 12.0.0(or the node version which you have recently installed).
5. Check your node version using node -v. It should show the node version which you asked to use in step 4.
6. That's it. Now you should use create-react-app and bootstrap the app again.

This worked like a charm for me. Hope someone facing same issue will find it helpful.

Update the minSdkVersion:

This could be an issue with getting jQuery to work with Electron. If you have Node integration turned on in your renderer process, jQuery will have issues loading because of some conflicting symbols it tries to define.

There's more information in the Electron FAQ.

The easiest way to solve this is to turn off nodeIntegration in your BrowserWindow.