-
- [x] I love this initiative, and would love for you to keep the commit history and own this repo, but we should probably transfer it into the yargs org once it's done: #3, #4, #5, #6, #9
- [x] I'm n…
-
Please consider upgrading yargs-parser.
```
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution …
-
**Describe the bug**
The error output for 2 similar user errors looks very different:
**MISSPELLED command parameter (new format in v3):**
Unable to perform this operation due to th…
-
Here's something that would be great for yargs in chat bots: an option to ignore case when matching commands. E.g., `yargs-o-matic command` could be fired regardless of whether the user typed `command…
-
```
Unknown arguments: auto-uppercase, autoUppercase
```
-
like the approach we're starting to take with http://istanbul.js.org/, I'd love to see us split our _very long_ yargs README document into various targeted tutorials. e.g.,
- using commands (CC: @nexd…
-
```
❯ npm audit
# npm audit report
axios
-
I want to implement an interface that collects all options after a positional option. The options are not known ahead of time.
Usage would look something like:
```sh
script.js --scriptOption scri…
-
Lodestar libraries depend on a number of external dependencies for historical reasons.
Identify dependencies that are not maintained anymore or can be considered a security risk.
- [ ] https://git…
-
Yargs 13.3.2 is currently using y18n 4.0.0 which has a pollution issue that shows up on vulnerability scans
Would it be possible to upgrade yargs to 16.2.0 which uses y18n 5.0.5 which fixes this?