You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using commander v3.0.0, I have a command that specifies the executableFile option:
program.name("testapp").version("1.0.0").command("list <type>","List available configuration",{executableFile: 'cli/list'})
The list command in cli/list.js specifies its name and some subcommands (only one listed for brevity):
program.name("list").description("List available configuration").command("secrets","Print all available secret types",{executableFile: 'list-secrets'})
Calling testapp list --help works as expected, but testapp help list throws an error. It appears help is trying to load cli-list.js rather than the file specified by executableFile.
$ testapp list --help
Usage: list [options] [command]
List available configuration
Options:
-h, --help output usage information
Commands:
secrets Print all available secret types
help [cmd] display help for [cmd]
$ testapp help list
error: cli-list(1) does not exist, try --help
The text was updated successfully, but these errors were encountered:
There is a Pull Request (thanks to @nazieb) which has been accepted onto the develop branch which should fix this: #1018
We have some other PR close to ready, but I think we might ship a v3.0.1 and not wait. It is great that people are using the new configuration option. I'll fix the TypeScript omission and then we could ship soon @abetomo ?
Using commander v3.0.0, I have a command that specifies the
executableFile
option:The
list
command incli/list.js
specifies its name and some subcommands (only one listed for brevity):Calling
testapp list --help
works as expected, buttestapp help list
throws an error. It appearshelp
is trying to loadcli-list.js
rather than the file specified byexecutableFile
.The text was updated successfully, but these errors were encountered: