Enforced maker options limit configuration

[publicvirtualvoid]

After some digging I realised that there are certain options for electron-builder that are hardcoded:

nx-electron/packages/nx-electron/src/executors/package/executor.ts

Line 151 in 7d0b59b

filter: ['main.js', '?(*.)preload.js', 'assets']

May I suggest that these are better generated as part of the default file itself such that the user still has the freedom to modify these?
In my case, I don't want to have my assets directory inside my .asar, so it is added as extraFiles.
I can't currently remove it from inclusion in the asar leading to them being included twice.

[bennymeg]

Excluding (or requiring the user explicitly define) the assets folder might confuse some users that just expects their application to function.
I would suggest adding an additional folder (i.e. '_assets') which you be able to include as an extra instead.

[publicvirtualvoid]

Would it not be better to include these in the default options file generated from the template? The application will function the same, but can be modified per application if needed.

[bennymeg]

Sounds like a good compromise. 🙂