Giters
npm
/
nopt
Node/npm Option Parsing
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
527
Watchers:
39
Issues:
54
Forks:
43
npm/nopt Issues
[BUG] SyntaxError: Unexpected token .
Closed
a year ago
Comments count
2
Reporting a vulnerability
Closed
a year ago
Comments count
1
New
Closed
2 years ago
[BUG] Parsing issues for options within a string on 4.0.x+
Updated
2 years ago
[BUG] --no-[parameterName] doesn't allow setting to null for some typeDefs
Updated
2 years ago
[BUG] Boolean arg swallows following arg if it is `false` or `true`
Updated
2 years ago
[BUG] no typeDef for Array
Updated
2 years ago
[BUG] nopt breaks on arguments passed in as numbers
Updated
2 years ago
Comments count
1
[FEATURE] Add a handler for *unknown* options, analogous to `invalidHandler`
Updated
2 years ago
Comments count
2
[DOCS] Read-me description inconsistent with actual handling of invalid option values
Updated
2 years ago
[BUG] Special characters (such as tab and space) do not correctly clean
Updated
2 years ago
Comments count
1
[BUG] Unexpected arguments not parsed correctly?
Updated
2 years ago
Comments count
3
[QUESTION] List of numbers ?
Updated
2 years ago
Comments count
2
[QUESTION] Option to disable auto-negation?
Updated
2 years ago
Comments count
2
[QUESTION] null values are objects?
Updated
2 years ago
[QUESTION] Why does nopt only work with cli args?
Updated
2 years ago
[QUESTION] Handling default values?
Updated
2 years ago
abbrev has no '1' version at all
Closed
2 years ago
Comments count
6
I am feeling
Closed
2 years ago
Can nopt not handle optional arguments to known options?
Closed
7 years ago
Comments count
2
The many2 : [path] example does not seem to work
Closed
7 years ago
Comments count
1
Setting type as [String] defaults string value to "true"
Closed
7 years ago
Comments count
1
Question: Is there any way to get lists without having to specify the option multiple times?
Closed
8 years ago
Comments count
1
Type objects not ===
Closed
8 years ago
Comments count
2
nopt and WebStorm 11
Closed
8 years ago
Comments count
1
3.0.5 release failing to install on my build server
Closed
9 years ago
Comments count
8
nopt.js:210 TypeError: Cannot read property 'name' of null
Closed
9 years ago
Comments count
2
undefined value on line 210
Closed
9 years ago
Comments count
1
How to have an option with-a-dash in the name?
Closed
9 years ago
Comments count
1
i want to give you a hug
Closed
9 years ago
Comments count
3
Glob patterns return unexpected results
Closed
9 years ago
Comments count
1
Get raw user input
Closed
10 years ago
Comments count
5
Is there any way to disable Abbreviations?
Closed
10 years ago
Comments count
4
path arrays not working for me?
Closed
10 years ago
Comments count
1
Arguments parsed to numbers incorrectly.
Closed
10 years ago
Comments count
10
path type with no argument appends true to cwd
Closed
10 years ago
Comments count
5
Unexpected string parsing
Closed
10 years ago
Comments count
1
Strange parsing results with multiple unknown flags
Closed
12 years ago
Comments count
4
unexpected arguments not parsed correctly?
Closed
11 years ago
Comments count
3
parse lone `-` as positional argument for `argv.remain` rather than ignoring it
Closed
11 years ago
Comments count
1
Double-expansion of short options
Closed
11 years ago
Comments count
2
Odd behavior with wrong keys
Closed
11 years ago
Comments count
1
usage statement
Closed
11 years ago
Comments count
2
Unknown option swallows a known one
Closed
11 years ago
Comments count
4
Short option parsing error
Closed
11 years ago
Comments count
3
Default handling of multi value args
Closed
12 years ago
Comments count
3
Odd behavior with wrong keys
Closed
12 years ago
Comments count
1
Rickrolled
Closed
13 years ago
Comments count
1
nopt is improperly handling "some" string values as numerics
Closed
13 years ago
license clarification
Closed
13 years ago
Previous
Next