Skip to content

Issues: npm/nopt

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.

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

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

Issues list

[BUG] Parsing issues for options within a string on 4.0.x+ Bug thing that needs fixing
#80 opened Apr 27, 2017 by calderas
[BUG] Boolean arg swallows following arg if it is false or true Bug thing that needs fixing
#72 opened Dec 5, 2016 by cspotcode
[QUESTION] Handling default values? Question further information is requested
#64 opened Jun 4, 2016 by robations
[QUESTION] Why does nopt only work with cli args? Question further information is requested
#63 opened May 8, 2016 by tkrugg
[QUESTION] null values are objects? Question further information is requested
#62 opened Apr 12, 2016 by markcellus
[BUG] no typeDef for Array Bug thing that needs fixing
#49 opened Aug 15, 2015 by stevenvachon
[QUESTION] Option to disable auto-negation? Question further information is requested
#47 opened Jun 26, 2015 by ghost
[BUG] nopt breaks on arguments passed in as numbers Bug thing that needs fixing
#42 opened Apr 16, 2015 by cueedee
[QUESTION] List of numbers ? Question further information is requested
#33 opened Mar 26, 2014 by kapouer
[BUG] Unexpected arguments not parsed correctly? Bug thing that needs fixing
#23 opened Sep 11, 2013 by cowboy
ProTip! Add no:assignee to see everything that’s not assigned.