The asar unpacked files are accessible only with functions like spawn/exec, see https://github.com/electron/electron/issues/6262

• electron-builder v11.2.4:

• ia32:

Hello,

There are two problems. The first one is that the regedit module is not saved automatically in app.asar.unpacked

The second problem is that it’s not really working even if I set manually the asarUnpack value.

builder.build ({
  // blabla
  config: {
    asarUnpack: [
      '**node_modules/regedit/**',
    ],
   }
  // blabla
})

The regedit module spawn/exec (I don’t know exactly) wsf and vbs scripts.

In the win.asar.unpacked directory I can find this module with all files. It looks perfect… C:\blabla\win-ia32-unpacked\resources\app.asar.unpacked\node_modules\regedit.

But when executing… it’s not working at all…

Input Error: Can not find script file "C:\blabla\win-ia32-unpacked\resources\app.asar\node_modules\regedit\vbs\regList.wsf".

Why the spawn/exec calls are not looking in the app.asar.unpacked directory? asarUnpack seems useless if it’s necessary to handle manually the location for the spawns. I’m doing something wrong?

Thanks for help Regards

[Skywalker13]

@develar I’ve make a module in order to handle this problem with only one line of code to add in the electron project, see https://github.com/epsitec-sa/hazardous

For example, with my sample:

'use strict';

require ('hazardous');
const regedit = require ('regedit');

regedit.list ('HKCU\\SOFTWARE', function (err, result) {
  if (err) {
    console.error (err);
    process.exit (1);
  }
  console.dir (result);
  process.exit (0);
});

The only thing to do is to add require ('hazardous'); at the beginning of the main script of the app. Then, the functions join(), resolve() and normalize() can return the unpacked location according to some conditions; just read the README for details.

[jononu]

It feels like the hazardous library should be the normal behavior for these functions. Is there a reason it’s not?

In our case we’re exec’ing a java on the system and running a JAR file that’s packaged with the app. It’s convoluted but saved us development effort by not having to rewrite some functions in node.