-
Notifications
You must be signed in to change notification settings - Fork 56
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
Switch from nomnom
to yargs
#356
Comments
This seems like a lot of work :( |
I don't think it would be too bad but |
suckkks. But probably an issue a lot of people are running into rn. We could make a really useful blog post about the conversion process once we do it |
👍 I would suggest the re-design shouldn't be done like copy&paste but more like @Frijol did for Lets call it a The only point I cannot measure up is existing tests are affected. |
Have you guys evaluated sindresorhus/meow? I know that sindresorhus uses promises as we do as well and he is very active. tj on the other hand has switched to using go and is not personally maintaining his modules. I haven't looked at them to closely to suggest anything thought. (edit: If I pinged sindresorhus or tj, sorry) |
I agree with @LinusU we should take a look on several other CLI solutions and have an eye on maintaining activities. I couldn't find any better than |
Yes, thanks for the plug @sindresorhus!
Please take a look at |
nomnom
to commander
nomnom
to yargs
Closing in favor of #722. |
We use
nomnom
to parse commands. It is apparently deprecated and no longer maintained. They suggest usingcommander
in the README but lots of folks recommendyargs
.The text was updated successfully, but these errors were encountered: