yargs vs argparse
Command-Line Argument Parsers Comparison
1 Year
yargsargparseSimilar Packages:
What's Command-Line Argument Parsers?

Command-line argument parsers are essential tools in Node.js development that help developers handle input parameters passed to scripts via the command line. They simplify the process of parsing command-line arguments, providing a structured way to define options, flags, and commands. These libraries enhance usability by allowing developers to create intuitive command-line interfaces (CLIs) for their applications, making it easier for users to interact with scripts and tools. Both Argparse and Yargs offer unique features and design philosophies that cater to different developer needs and preferences.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
yargs101,045,89411,183292 kB3192 years agoMIT
argparse100,075,325494-54 years agoPython-2.0
Feature Comparison: yargs vs argparse

Ease of Use

  • yargs:

    Yargs offers a more extensive API with a focus on usability. It supports chaining methods for defining commands and options, making it easy to create complex command-line interfaces. Its built-in help and versioning features enhance user experience.

  • argparse:

    Argparse is designed to be simple and intuitive, making it easy for developers to define command-line arguments and options. Its API is straightforward, allowing you to quickly set up argument parsing with minimal boilerplate code.

Feature Set

  • yargs:

    Yargs boasts a rich feature set, including support for commands, middleware, and dynamic argument parsing. It allows you to create subcommands and manage complex argument structures, making it a powerful choice for building sophisticated CLIs.

  • argparse:

    Argparse provides essential features for argument parsing, including positional arguments, optional flags, and type validation. However, it lacks advanced features like command handling and middleware support, making it less suitable for complex applications.

Documentation and Community Support

  • yargs:

    Yargs has extensive documentation and a larger community, providing a wealth of resources, tutorials, and examples. This makes it easier for developers to find help and best practices when using the library.

  • argparse:

    Argparse has decent documentation, but its community is smaller compared to Yargs. This may lead to fewer resources and examples available for troubleshooting or learning.

Performance

  • yargs:

    Yargs is also performant but may introduce slight overhead due to its richer feature set. However, this overhead is generally negligible for most applications, especially when the benefits of its advanced features are considered.

  • argparse:

    Argparse is lightweight and performs well for simple argument parsing tasks. Its minimalistic design means it has lower overhead, making it suitable for small scripts and utilities.

Customization and Extensibility

  • yargs:

    Yargs excels in customization and extensibility, allowing developers to create custom commands, middleware, and validation logic. This flexibility makes it a better choice for applications that require tailored command-line interfaces.

  • argparse:

    Argparse offers basic customization options for argument parsing but lacks the extensibility features found in more advanced libraries. It is suitable for straightforward use cases without the need for extensive customization.

How to Choose: yargs vs argparse
  • yargs:

    Choose Yargs if you require a more feature-rich solution with advanced capabilities such as command chaining, middleware support, and built-in help generation. Yargs is ideal for larger applications where a more extensive command-line interface is needed.

  • argparse:

    Choose Argparse if you need a straightforward and minimalistic approach to argument parsing, especially if you are familiar with Python's argparse library. It is suitable for simple scripts where you want to define options and arguments without additional complexity.

README for yargs

Yargs

Yargs be a node.js library fer hearties tryin' ter parse optstrings


ci NPM version js-standard-style Coverage Conventional Commits Slack

Description

Yargs helps you build interactive command line tools, by parsing arguments and generating an elegant user interface.

It gives you:

  • commands and (grouped) options (my-program.js serve --port=5000).
  • a dynamically generated help menu based on your arguments:
mocha [spec..]

Run tests with Mocha

Commands
  mocha inspect [spec..]  Run tests with Mocha                         [default]
  mocha init <path>       create a client-side Mocha setup at <path>

Rules & Behavior
  --allow-uncaught           Allow uncaught errors to propagate        [boolean]
  --async-only, -A           Require all tests to use a callback (async) or
                             return a Promise                          [boolean]
  • bash-completion shortcuts for commands and options.
  • and tons more.

Installation

Stable version:

npm i yargs

Bleeding edge version with the most recent features:

npm i yargs@next

Usage

Simple Example

#!/usr/bin/env node
const yargs = require('yargs/yargs')
const { hideBin } = require('yargs/helpers')
const argv = yargs(hideBin(process.argv)).argv

if (argv.ships > 3 && argv.distance < 53.5) {
  console.log('Plunder more riffiwobbles!')
} else {
  console.log('Retreat from the xupptumblers!')
}
$ ./plunder.js --ships=4 --distance=22
Plunder more riffiwobbles!

$ ./plunder.js --ships 12 --distance 98.7
Retreat from the xupptumblers!

Note: hideBin is a shorthand for process.argv.slice(2). It has the benefit that it takes into account variations in some environments, e.g., Electron.

Complex Example

#!/usr/bin/env node
const yargs = require('yargs/yargs')
const { hideBin } = require('yargs/helpers')

yargs(hideBin(process.argv))
  .command('serve [port]', 'start the server', (yargs) => {
    return yargs
      .positional('port', {
        describe: 'port to bind on',
        default: 5000
      })
  }, (argv) => {
    if (argv.verbose) console.info(`start server on :${argv.port}`)
    serve(argv.port)
  })
  .option('verbose', {
    alias: 'v',
    type: 'boolean',
    description: 'Run with verbose logging'
  })
  .parse()

Run the example above with --help to see the help for the application.

Supported Platforms

TypeScript

yargs has type definitions at @types/yargs.

npm i @types/yargs --save-dev

See usage examples in docs.

Deno

As of v16, yargs supports Deno:

import yargs from 'https://deno.land/x/yargs/deno.ts'
import { Arguments } from 'https://deno.land/x/yargs/deno-types.ts'

yargs(Deno.args)
  .command('download <files...>', 'download a list of files', (yargs: any) => {
    return yargs.positional('files', {
      describe: 'a list of files to do something with'
    })
  }, (argv: Arguments) => {
    console.info(argv)
  })
  .strictCommands()
  .demandCommand(1)
  .parse()

ESM

As of v16,yargs supports ESM imports:

import yargs from 'yargs'
import { hideBin } from 'yargs/helpers'

yargs(hideBin(process.argv))
  .command('curl <url>', 'fetch the contents of the URL', () => {}, (argv) => {
    console.info(argv)
  })
  .demandCommand(1)
  .parse()

Usage in Browser

See examples of using yargs in the browser in docs.

Community

Having problems? want to contribute? join our community slack.

Documentation

Table of Contents

Supported Node.js Versions

Libraries in this ecosystem make a best effort to track Node.js' release schedule. Here's a post on why we think this is important.