Packaging library with `electron-packager` under `win32`

[TheLambdaFunction]

Hello again 😆 ,

I've found out that current versions of electron-packager and electron-asar have a rule that does not allow execution of binaries shipped in the ASAR file. This unfortunately break the win32 side of this library.

The solution/workaround is to configure electron-packager to unpack the contents of the easy-volume library aside the final executable.
Something like this:

--asar.unpack '**/easy-volume/dist/platforms/windows/**'

Also, because this argument is not supported when passed from command line (at least that's what I've seen so far) one is forced to create a JS script file and use that to invoke the electron-packager APIs accordingly.

Not sure if there's anything you can do on your side of things, I just wanted to point this out and leave a trace for the developers stumbling on this issue

[Arciiix]

Hey,

Thanks so much for the heads-up and for taking time to document this, I really appreciate it!

Interestingly, this used to work just fine in earlier versions of electron-packager, in fact easy-volume was created for this purpose, so it's definitely a new issue. I hadn’t run into this limitation before with binaries inside ASAR, so your note is especially helpful in pinpointing the cause.

As you said, sadly I'm not sure if there's much I can do. When I find some free time, I'll try to dig into it and see if there's anything I can do.

Thanks again!

[YaAvi]

If you're using electron forge you can do:

packagerConfig: {
    asar: {
      unpack: '**/easy-volume/dist/platforms/windows/**'
    }
}

in your forge.config.js file.
a more general way:

packagerConfig: {
  asar: {
    unpack: "{path/to/*.exe, path/to/**/*.node}"
  }
}