[@types/yargs] command/usage returned type doesn't include the commands defined arguments

[segevfiner]

The returned object from yargs parsing include the arguments of the sub-command that was ran. Sometimes instead of using handler, you want to parse the arguments of the main program only, or handle commands in some other way:

const argv = yargs(hideBin(process.argv))
  .command("$0 <file>", "", (yargs) => {
    return yargs.positional("file", { type: "string" });
  }, (argv) => {
    console.log(argv);
  })
  .strict()
  .parseSync();
console.log(argv);

Inside the handler, you have types for the file argument, but outside of it, you don't. Despite both console.log printing the same.

Also, it seems you need to return the yargs from the builder argument of the command for types to work, which is not documented in the official yargs docs, and you might want to document this more clearly in the TSDoc of the command and usage methods.

[typescript-bot]

Thanks for the discussion about "yargs", some useful links for everyone:

• npm
• DT
• Related discussions

Pinging the DT module owners: @poelstra, @mizunashi-mana, @pushplay, @JimiC, @steffenvv, @forivall, @ExE-Boss, @Aankhen, @bcoe.

[segevfiner]

Ping? @poelstra, @mizunashi-mana, @pushplay, @JimiC, @steffenvv, @forivall, @ExE-Boss, @Aankhen, @bcoe

[forivall]

Feel free to open a PR! Let us know if you need help.