update nopt dependency about findup

[Filirom1]

Because of the the cli https://github.com/Filirom1/findup/blob/master/bin/findup.js that use this Pull Request npm/nopt#13.

An other option would be to use commander instead of nopt.

[mike-spainhower]

👍

@Filirom I would be happy to PR this to close the issue. Which approach do you prefer: moving from nopt to commander or publishing nopt-usage as suggested by isaac?

I am on a mission to remove all GH tarballs from all my upstream deps for reasons explained here - browserify/browserify#683

[Filirom1]

Do it the way you prefer ;-)

[rowdyrabbit]

Yes, it would be great if the nopt dependency could point to a version rather than the GH tarball - I'm having an issue at work where the corporate ntlm proxy can't handle the https GH url and therefore my npm install is failing. This really sucks because I want my team and I to be able to install yeoman, but it has a dependency on findup and therefore nopt. I seem to be having the same issue as this person: yeoman/yeoman#1274

[rowdyrabbit]

Could I update the dependency on nopt to point to version 2.2.0 (https://www.npmjs.org/package/nopt) instead of your GH url?

[Filirom1]

You could update nopt, but the cli will not work because of : npm/nopt#13.
You could replace nopt by commander if you want, or create a nopt-usage library based on the PR.