Dependency not included in packaged application because it contains executable code

[ku4ndev]

• Electron-Builder Version: 25.0.5

• Node Version: 22.5.1

• Electron Version: 31.1.0
• Electron Type (current, beta, nightly): Not using electron-updater

• Target: Windows, portable

Hello,

The application I'm developing uses the java-bridge NPM package in order to use a JAR inside the application.
Everything runs fine when just running the application, but when packaging it doesn't (the first call that depends on java-bridge fails).

During the packaging process, the console shows that java-bridge is not being included in the asar archive because it contains executable code. I tried including those files using "asarUnpack" in package.json but it still doesn't work (tried both the portable executable aswell as the unpacked application).

I understand that this is due to security concerns; I was wondering if someone has been in the same situation and/or there is a workaround for this.

If there is any other relevant information I can provide let me know and I will provide it as soon as possible.

Thank you beforehand :)

[mmaietta]

the console shows that java-bridge is not being included in the asar archive because it contains executable code

Is java-bridge not showing up in the app.asar.unpacked folder? Off the top of my head, that's the default behavior when encountering executable code.

[ku4ndev]

It is there although its missing some files when comparing the content with node_modules/java-bridge.
Could the files show up in app.asar.unpacked but be a reference issue? If so, do I have to treat dependencies outside of asar archive a bit different maybe?

[mmaietta]

The files may be within the app.asar as the asar contains the metadata record of files-within-asar and symlinks-to-asar-unpacked, dependencies outside the asar should automatically be handled by the asar reader.

The best way for you to check that your app has all files/dependencies required, you can run npx asar extract <asar path> <out dir> and check the package contents/structure (it'll include both packed and unpacked files)