Home / npm packages / yargs-parser

yargs-parser source code

Every file of yargs-parser@22.0.0 as published on npm: 10 files, 86 KB. Search them by exact text or regex, in milliseconds.

It uses: process.env, the fs module.

What yargs-parser uses

APIIn yargs-parser
eval()
runs a string as JavaScript
NoWho does
new Function()
builds a function from a string, like eval (with or without new)
NoWho does
child_process
starts other programs
NoWho does
process.env
reads environment variables
Yes: 2 files
e.g. build/lib/index.js
See the lines
the fs module
reads and writes files
Yes: 1 file
e.g. build/lib/index.js
See the lines
http / https
makes or serves HTTP requests with Node's own modules
NoWho does
fetch()
makes HTTP requests
NoWho does
XMLHttpRequest
makes HTTP requests the old browser way
NoWho does
crypto
hashes, encrypts or makes random numbers
NoWho does
WebAssembly
loads WebAssembly code
NoWho does
document.cookie
reads or writes browser cookies
NoWho does
install scripts
runs a script when it's installed
NoWho does

Exact matches in the published files, so a mention in a comment counts too: open the lines to check.

Largest files

FileSize
build/lib/yargs-parser.js47 KB
CHANGELOG.md17 KB
README.md12 KB
build/lib/index.js2.6 KB
build/lib/string-utils.js2.1 KB
package.json2.0 KB
build/lib/tokenize-arg-string.js1.1 KB
browser.js1.0 KB
LICENSE.txt731 B
build/lib/yargs-parser-types.js425 B

Questions

How many files are in yargs-parser?

Version 22.0.0 of yargs-parser publishes 10 files of source, 86 KB in all, not counting images, fonts and source maps.

Does yargs-parser use eval?

No: yargs-parser doesn't call eval() anywhere in its published files.

Does yargs-parser start other programs?

No: yargs-parser doesn't use child_process anywhere in its published files.

Does yargs-parser run an install script?

No: yargs-parser has no preinstall, install or postinstall script in its package.json.

npm packages that use…

Every package we've indexed →

Search your own code like this

The same engine answers over your documents and repositories: exact text and regex, every match counted, from your code or your AI agent.

See StackGrep Engine