Skip to content
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

Move to yargs #70

Closed
kentcdodds opened this issue Oct 4, 2016 · 5 comments
Closed

Move to yargs #70

kentcdodds opened this issue Oct 4, 2016 · 5 comments

Comments

@kentcdodds
Copy link
Collaborator

Commander is cool and all, but there's some hacky things we have to do to get our CLI to do what we want. It'd be sweet to use yargs which is much more flexible.

All changes should happen in here. Should hopefully be able to just use it similar to how I've used it in split-guide here 👍

@sxn
Copy link
Collaborator

sxn commented Oct 4, 2016

That's a pretty solid starting point! 👍
Some things that should change here as well, from the looks of it, right?

@kentcdodds
Copy link
Collaborator Author

Yes, probably so...

@nkbt
Copy link
Collaborator

nkbt commented Oct 4, 2016

I actually found nomnom to be the best. Just in case you've never heard of it http://npm.im/nomnom

@kentcdodds
Copy link
Collaborator Author

I've never used nomnom, but I have used yargs and liked it pretty well. It's also much more widely used. I think I'd like to stick with that one personally. What do you think @sxn?

@sxn
Copy link
Collaborator

sxn commented Oct 6, 2016

Hm. Actually I hadn't played around with either of those, so I can't form an informed opinion. I'll briefly look into both before diving in and come back. Without looking into them I'd probably choose {{yargs}} just because there would be at least one person who knows this codebase and the library we'd be introducing. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants