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
I'm building a command line utility to interface with an API that I've built. The node utility is currently using commander to parse CLI arguments and cli-config to setup and maintain a user-specific configuration file.
The problem that I'm having is that the two packages are trying to do the same thing. The [cli] option of cli-config is attempting to interpret the command land arguments that are passed into the script, when I really want command to interpret them.
Is there a way to disable argument parsing or remove the minimist integration?
The text was updated successfully, but these errors were encountered:
I was ready to use this package in my simple utility but I ran into the same problem. I have more sophisticated ways to parse command line arguments and I don't want to use minimist for this...
I'm building a command line utility to interface with an API that I've built. The node utility is currently using commander to parse CLI arguments and cli-config to setup and maintain a user-specific configuration file.
The problem that I'm having is that the two packages are trying to do the same thing. The [cli] option of cli-config is attempting to interpret the command land arguments that are passed into the script, when I really want command to interpret them.
Is there a way to disable argument parsing or remove the minimist integration?
The text was updated successfully, but these errors were encountered: