Skip to content

Issues: pkgjs/parseargs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
19 Open 50 Closed
19 Open 50 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

parseArgs in runtimes where global is not defined
#157 by kisaragi-hiu was closed Sep 14, 2024
1
3
Second argument (first in process.argv) is always ignored.
#146 by SpacingBat3 was closed Oct 28, 2022
5
What's the minimum required Node.js version for this package?
#131 by haoqunjiang was closed Jun 20, 2022
1
5
What is happening with process.mainArgs?
#128 by shadowspawn was closed Sep 4, 2022
2
Unify custom error codes?
#120 by shadowspawn was closed Apr 25, 2022
4
Restructure result conventions (again again)
#119 by aaronccasanova was closed Apr 23, 2022
@aaronccasanova
6
docs: add strict:false example to upstream ? documentation Improvements or additions to documentation
#114 by shadowspawn was closed Sep 4, 2022
3
Kudos Benjamin Coe
#109 by shadowspawn was closed May 24, 2022
2
null prototype for returned values? enhancement New feature or request
#108 by shadowspawn was closed Apr 17, 2022
1
@shadowspawn
19
Add placeholder for upstream docs?
#107 by shadowspawn was closed Apr 17, 2022
1
2
Refactor tests?
#105 by shadowspawn was closed Apr 14, 2022
1
1
More pollution protection? enhancement New feature or request
#104 by shadowspawn was closed Apr 15, 2022
1
@shadowspawn
5
security: switch to using Map during parsing enhancement New feature or request
#99 by bcoe was closed Apr 14, 2022
4
Make type mandatory for configured options
#94 by bakkot was closed Apr 10, 2022
1
2
🔨 Moving towards MVP Milestone 1
#87 by shadowspawn was closed Apr 13, 2022
6
Should positionals be opt-in when strict: true? enhancement New feature or request
#85 by bakkot was closed Apr 18, 2022
1
40
Reporting indexes enhancement New feature or request
#84 by bakkot was closed Jul 20, 2022
1
21
How might I add support for defaults? (And env?) bring-your-own-code Experiments with how authors might build on parseArgs
#82 by shadowspawn was closed Oct 15, 2022
11
Syntax for combined short option and value discussion
#78 by shadowspawn was closed Mar 30, 2022
2
Make "type: string" options greedy? enhancement New feature or request
#77 by shadowspawn was closed Apr 19, 2022
1
21
How might I add my own support for negative numbers? bring-your-own-code Experiments with how authors might build on parseArgs
#72 by shadowspawn was closed Aug 29, 2022
1
Restructure result conventions (again) discussion
#70 by shadowspawn was closed Apr 13, 2022 Merge into Node.js
29
Multiple test files?
#66 by shadowspawn was closed Feb 27, 2022
2
Support for short options with numeric values, e.g, -p80 enhancement New feature or request
#60 by bcoe was closed Mar 30, 2022
9
should "--" signal an end to parsing? discussion
#58 by bcoe was closed Mar 30, 2022
4
ProTip! Adding no:label will show everything without a label.