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

Switch Optimist with Minimalist -> Deprecation notice #441

Closed
stephnr opened this issue Jul 28, 2015 · 10 comments
Closed

Switch Optimist with Minimalist -> Deprecation notice #441

stephnr opened this issue Jul 28, 2015 · 10 comments

Comments

@stephnr
Copy link
Contributor

stephnr commented Jul 28, 2015

I was running through bin/jest.js and noticed that the Optimist plugin issued a deprecation notice and recommends changing to use minimist instead.

I would be willing to make this conversion going ahead 👍

@ide
Copy link
Contributor

ide commented Aug 13, 2015

I imagine a PR would be appreciated if you want to contribute one when you have time.

@cpojer
Copy link
Member

cpojer commented Aug 13, 2015

There is also nomnom which we have been using for https://github.com/facebook/jscodeshift

@mbrio
Copy link
Contributor

mbrio commented Mar 15, 2016

If no one is working on this, I'd be willing to do the migration. I guess the question is what would be the best library. Optimist specifically mentions yargs as it's replacement which I believe is 100% compatible, is active, and has a large following. If the argument is that Optimist is deprecated and Jest should be using a non-deprecated library then yargs may be the better solution as there would be code changes if we use Minimist. If we are going to spend any time changing code then we'd probably be better off as @cpojer says and use what the other FB projects are using.

@cpojer
Copy link
Member

cpojer commented Mar 15, 2016

@fkling what would you recommend? I remember we had this discussion around jscodeshift as well.

@mbrio it would be awesome if you could take this on! I'll try to merge #800 today, it probably makes sense to wait for that first :)

@mbrio
Copy link
Contributor

mbrio commented Mar 16, 2016

Sounds good, I'll keep my ear out for this. Tomorrow may be hard for me, but I'll get to it this week.

@cpojer
Copy link
Member

cpojer commented Mar 16, 2016

Alright, the refactor from #800 has now landed!

@cpojer
Copy link
Member

cpojer commented May 20, 2016

I'm gonna close this because I honestly don't really care much about it. It works just fine. @DmitriiAbramov is thinking of redoing some stuff here, so maybe he can consider to replace this module eventually.

@cpojer cpojer closed this as completed May 20, 2016
@aaronabramov
Copy link
Contributor

👍
I think for this change we need to have at least a small design doc that will list the requirements for CLI, and based on this we can decide which library we should use

@cpojer
Copy link
Member

cpojer commented May 20, 2016

I agree. The deprecation notice itself is not enough for anyone at FB to spend time working on this.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants