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
If your command files use the .js extension, but you run the command via node mycommand instead of node mycommand.js, any git-style sub-commands will fail in Command.prototype#executeSubCommand
This failure is on line 531, column 15 of index.js:
This is causing an error because Commander is looking for the file that corresponds to argv[1], so in this specific case, argv[1] doesn't match the actual file name.
The text was updated successfully, but these errors were encountered:
If your command files use the
.js
extension, but you run the command vianode mycommand
instead ofnode mycommand.js
, any git-style sub-commands will fail inCommand.prototype#executeSubCommand
This failure is on line 531, column 15 of
index.js
:Specifically this part is failing:
This is causing an error because Commander is looking for the file that corresponds to argv[1], so in this specific case, argv[1] doesn't match the actual file name.
The text was updated successfully, but these errors were encountered: