Hi guys,
I have a problem no other command line parsing library I've explored (probably) supports and since the generality of yargs, maybe you have some solution for it, but I can't really tell as from many options you provide, I'm a bit lost :).
I want to get a list of possibly multiple commands with arguments in a row as defined on the command line, so that I can build from it a "functional pipeline", that will be applied to some array/iterator/stream.
Is this case somehow solvable with yargs?
Many thanks...
Had a quick question. I am building a CLI using yargs and want to give users the options to add their own commands in a specific folder. I know I can use the following to accomplish this:
.commandDir(path.join(process.cwd(), 'commands))This works great when the folder exists in the project, but if it does exist I get the following error:
Error: Error: ENOENT: no such file or directory, scandir 'DIRECTORY_PATH'is there a way add the command directory ONLY if the directory exists?
thanks.
yargs supports command lines as the following: myprog -r repo -v clone -p proj -a, i.e. having arguments (-r, -v) that are available for each command and are specified before it and arguments that are only valid for a specific command (-p, -a). Similar to https://git-scm.com/docs/git. I tried using something like yargs.option(...).command(...) but that did not seem to work.
https://raw.githubusercontent.com/yargs/yargs/v15.4.1/docs/api.md returns 404 for me
I have developed a framework for
yargs, that is really easy to use, supports subCommands (which is one of the thing why a lot of people use yargs), and it was intended to be testable by default.https://github.com/nugaon/furious-commander
if you like it, please leave a star on the project ^^
else if ! you like it, leave an
issue why
"test mocha 'tests/**/*.test.js'" in my package.json. As far as I understand I can pass some custom params only like this npm run test -- --myCustomArg=foo. Can I somehow shorten it to be script --yargs ?
.option on yargs itself. It makes those options global and they exist on all sub-commands as well as the top-level executable. I do not want this behaviour. How do I accomplish this?
@ljharb I think you misunderstood. or I miss-explained. Consider the following example:
const yargs = require("yargs");
(async () => {
const options = await yargs
.option("config", {
type: "string",
alias: "c",
//global: false,
})
.command("hello", "description for hello command")
.demandCommand().argv;
console.log(options);
})();When invoked like the following:
$ <program> hello --helpit's help output is:
<program> <command>
Commands:
<program> hello description for hello command
Options:
--help Show help [boolean]
--version Show version number [boolean]
-c, --config [string]In my optinion the --config options should not appear on the hello command. As i understand it, this is documented as options being "global" by default. But setting global to false does not help.
Thanks for the help!
--version option also exists on the sub-command. Which is not desireable.
--config on everything?
global: true doesn't mean this, what it means is that it will be hoisted above middleware. everything is global:false by default)
.hide('config') or something