+2
-2
| { | ||
| "name": "nopt", | ||
| "version": "10.0.0", | ||
| "version": "10.0.1", | ||
| "description": "Option parsing for Node, supporting types, shorthands, etc. Used by npm.", | ||
@@ -31,3 +31,3 @@ "author": "GitHub Inc.", | ||
| "devDependencies": { | ||
| "@npmcli/eslint-config": "^6.0.0", | ||
| "@npmcli/eslint-config": "^7.0.0", | ||
| "@npmcli/template-oss": "5.1.0" | ||
@@ -34,0 +34,0 @@ }, |
+2
-4
@@ -144,6 +144,4 @@ If you want to write an option parser, and have it be good, there are | ||
| By default nopt logs debug messages if `DEBUG_NOPT` or `NOPT_DEBUG` are set in the environment. | ||
| You can assign the following methods to `nopt` for notification of invalid, unknown, and expanding options: | ||
| You can assign the following methods to `nopt` for a more granular notification of invalid, unknown, and expanding options: | ||
| `nopt.invalidHandler(key, value, type, data)` - Called when a value is invalid for its option. | ||
@@ -153,3 +151,3 @@ `nopt.unknownHandler(key, next)` - Called when an option is found that has no configuration. In certain situations the next option on the command line will be parsed on its own instead of as part of the unknown option. In this case `next` will contain that option. | ||
| You can also set any of these to `false` to disable the debugging messages that they generate. | ||
| You can set any of these to `false` or leave them unset to skip that notification. | ||
@@ -156,0 +154,0 @@ ## Abbreviations |
26511
-0.47%213
-0.93%