Explicitly setting asar to false gives a warning

[XuluWarrior]

• [ x ] I have read the contribution documentation for this project.
• [ x ] I agree to follow the code of conduct that this project follows, as appropriate.
• [ x ] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
Adding --asar=false to the command line gives the warning
WARNING: asar parameter set to an invalid value (false), ignoring and disabling asar

I realise that false is the default value but sometimes it aids clarity to set parameters explicitly.

[malept]

Due to how minimist works (the command line argument parser we use), you need to specify --no-asar instead of --asar=false (which makes it think the value of the argument is the string "false").

[XuluWarrior]

Is the option --no-asar or your use of minimist syntax documented anywhere? I can't find it in usage.txt or api.md

In fact api.md states

asar

Boolean or Object (default: false)

[malept]

Well, there's --no-prune. There's an issue in minimist about documenting --no-.

The API docs are written with the JS API in mind.

[malept]

[...] sometimes it aids clarity to set parameters explicitly.

I would suggest instead of using the CLI, instead use the JavaScript API and enumerate all of the Packager options in a build.js file. Otherwise, you're going to hit "command too long" problems.