yargs

Yargs is a Node.js library for building interactive command-line tools. It parses process arguments into a structured object, generates a dynamic, well-formatted help menu, and provides a full command-routing system so a single executable can expose subcommands the way git or docker do.

Beyond simple flag parsing, yargs handles positional and grouped options, required-argument and mutually-exclusive-option validation, default values, environment-variable and config-file loading, custom coercion, and async command handlers with middleware. It also generates Bash and Zsh completion scripts automatically, so CLIs built on yargs get shell autocomplete with no extra work.

It ships as ESM with first-class TypeScript typings, and runs across Node.js, Deno, and the browser via platform shims, making it a common foundation layer under many popular CLI tools in the JavaScript ecosystem.

What You Get

• A .command() API for defining subcommands, positional arguments, and nested command hierarchies, with a default command marker ($0/*) for single-command CLIs
• Automatic, dynamically generated --help output and usage strings, grouped by option category
• Built-in Bash and Zsh completion script generation via .completion()
• Global and per-command middleware (.middleware()) that can run before or after argument validation, including mutation-aware middleware
• Declarative validation: .demandOption(), .conflicts(), .implies(), .check(), and custom failure handlers via .fail()
• Config loading from files, environment variables (.env()), and .pkgConf() for package.json-based configuration
• First-class TypeScript typings that infer the shape of the parsed argv object from the options you declare

Common Use Cases

• Building a multi-command CLI tool (e.g. mytool serve, mytool init <path>) with per-command options and help text
• Parsing flags for a single-purpose script (--verbose, --port=5000) without building a full command tree
• Adding shell tab-completion to a published CLI package
• Validating required/conflicting CLI options before a command handler runs, via middleware or .check()
• Loading CLI configuration from environment variables or a config file alongside command-line flags

Under The Hood

Architecture Yargs is built as a platform-agnostic factory: YargsFactory() in lib/yargs-factory.ts accepts a PlatformShim (implemented separately for CJS/Node, ESM, Deno, and browser targets in lib/platform-shims/) and returns a constructor for YargsInstance, which composes several focused subsystems — CommandInstance (lib/command.ts) for subcommand registration, dispatch, and default-command handling; UsageInstance (lib/usage.ts) for help-text generation; ValidationInstance (lib/validation.ts) for option-conflict and requirement checks; GlobalMiddleware (lib/middleware.ts) for pre/post-validation hooks; and CompletionInstance (lib/completion.ts) for shell completion scripts. Parsing itself is delegated to the separate yargs-parser package, keeping tokenization decoupled from command routing and help generation. This shim-based design is what lets the same core logic run identically across Node, Deno, and the browser.

Tech Stack Written in TypeScript, compiled via tsc against gts (Google’s TypeScript style preset) into a build/ directory, then re-exported through a small ESM entrypoint (index.mjs) that wires the compiled factory to the Node platform shim; a parallel deno.ts entrypoint targets Deno directly. Runtime dependencies are deliberately minimal and modular: yargs-parser for tokenization, cliui for column-aligned help layout, string-width for unicode-aware text wrapping, y18n for i18n of built-in messages, escalade and get-caller-file for filesystem/caller resolution. The package is pure ESM ("type": "module") with generated .d.ts typings shipped for consumers.

Code Quality Tests live under test/*.mjs and are run with Mocha plus c8 for coverage, with a check:coverage step enforced in CI; the suite is extensive, covering command parsing, middleware ordering, validation rules, completion generation, and both ESM and CJS/Deno integration paths separately. Linting runs through gts lint (an opinionated ESLint/Prettier preset) as part of the check script, and CI (GitHub Actions) runs compile, lint, and test on every push. Error handling is centralized through a custom YError type rather than raw thrown strings, and public API entry points are guarded with argsert() runtime type assertions.

What Makes It Unique Yargs’ distinguishing choice is treating help-text generation, shell completion, and validation as first-class, automatically derived features of the same command/option declarations used for parsing — rather than requiring a CLI author to hand-write help strings or completion scripts separately. Its shim-based platform abstraction (one core, multiple platform adapters for Node/Deno/browser/ESM/CJS) is also relatively unusual among CLI-parsing libraries, most of which target a single runtime.