Commander.js: Please add .command() function a path config

[winys]

It would be better if we can customize the path of sub-command file.

[dszakallas]

Our naming policy enforces camel case for filenames, but subcommands are more naturally written in kebab case. Currently commander doesn't do this mapping neither gives an option for me to do it manually. It would be great if there would be either

• camelize option for subcommands or
• a way to configure the executables` path.

[shadowspawn]

Pull Request #854 adds an option for this.

I am interested in feedback on executableFile as the option name?

e.g.

.command("example", "example description", { executableFile: "myExampleCommand" });

[shadowspawn]

Pull Request #999 is being considered for v3, adds option to override executable file name

[shadowspawn]

This issue will be resolved when v3.0.0 is released. Available now as a prerelease. See #1001

[shadowspawn]

.command now supports the executableFile option (thanks to @abetomo).
Shipped in v3: https://github.com/tj/commander.js/releases/tag/v3.0.0