Observed since 20 Oct, 08:15 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
yargs
Light-weight option parsing with an argv hash. No optstrings attached.
Yargs be a node.js library fer hearties tryin' ter parse optstrings
Yargs helps you build interactive command line tools, by parsing arguments and generating an elegant user interface.
It gives you:
my-program.js serve --port=5000).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]
Stable version:
npm i yargs
Bleeding edge version with the most recent features:
npm i yargs@next
#!/usr/bin/env node
import yargs from 'yargs';
import { hideBin } from 'yargs/helpers';
const argv = yargs(hideBin(process.argv)).parse()
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:
hideBinis a shorthand forprocess.argv.slice(2). It has the benefit that it takes into account variations in some environments, e.g., Electron.
#!/usr/bin/env node
import yargs from 'yargs';
import { hideBin } from '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.
yargs has type definitions at @types/yargs.
npm i @types/yargs --save-dev
See usage examples in docs.
As of v16, yargs supports Deno:
import yargs from 'https://deno.land/x/yargs@v17.7.2-deno/deno.ts'
import { Arguments } from 'https://deno.land/x/yargs@v17.7.2-deno/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()
Note: If you use version tags in url then you also have to add
-denoflag on the end, like@17.7.2-deno
See examples of using yargs in the browser in docs.
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.
npm · 1 observations shown. Missing days are unknown.
| Date / source period | Value | Observed at |
|---|---|---|
| 2026-10-20 | 8 | 2026-10-20T09:43:02.7403766Z |
| Package / target | Requirement | Relationship |
|---|---|---|
minimistEnvironment{
"local_name": "minimist",
"alias": false,
"peer_metadata": null
} | ~0.0.1 | runtime |
tapEnvironment{
"local_name": "tap",
"alias": false,
"peer_metadata": null
} | ~0.4.0 | development |
hashishEnvironment{
"local_name": "hashish",
"alias": false,
"peer_metadata": null
} | ~0.0.4 | development |
Source distribution
{
"shasum": "c0fe4988495615c98e51c12b700783aa3ee2c0f6",
"tarball": "https://registry.npmjs.org/yargs/-/yargs-1.0.15.tgz",
"integrity": "sha512-9xV6HtYn3YSyCE+bQhBoEJBGZjVglD8ODMYpLiY2aovMs8p0aVEDMGYyp9QM+oEtsm+F/PUQOS0NfRtEAvj2IA==",
"signatures": [
{
"sig": "MEYCIQD8sOlBzEGnaKBA67KNFKCpRCOTcfwtmS9GI39ji9VhOwIhAMzj2c2CWWu3jQMv732dnQ1oBOCCQKDTxZhf5k7s56cM",
"keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"
}
]
}Observed since 20 Oct, 08:15 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package_version:621ea7e7fc7f0a3c3119d28f1bbbb237d9c80d40aae8ea25bb2254de44ccf425