Comparing version 3.0.2 to 3.0.3
{ | ||
"name": "nopt", | ||
"version": "3.0.2", | ||
"version": "3.0.3", | ||
"description": "Option parsing for Node, supporting types, shorthands, etc. Used by npm.", | ||
@@ -17,4 +17,4 @@ "author": "Isaac Z. Schlueter <i@izs.me> (http://blog.izs.me/)", | ||
"devDependencies": { | ||
"tap": "~0.4.8" | ||
"tap": "^1.2.0" | ||
} | ||
} |
@@ -8,5 +8,6 @@ If you want to write an option parser, and have it be good, there are | ||
The Right Way is to write some complex configurable program with so many | ||
options that you go half-insane just trying to manage them all, and put | ||
it off with duct-tape solutions until you see exactly to the core of the | ||
problem, and finally snap and write an awesome option parser. | ||
options that you hit the limit of your frustration just trying to | ||
manage them all, and defer it with duct-tape solutions until you see | ||
exactly to the core of the problem, and finally snap and write an | ||
awesome option parser. | ||
@@ -13,0 +14,0 @@ If you want to write an option parser, don't write an option parser. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
30447
9
211