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

Expose yargs-parser #1475

Closed
coreyfarrell opened this issue Nov 9, 2019 · 1 comment · Fixed by #1477
Closed

Expose yargs-parser #1475

coreyfarrell opened this issue Nov 9, 2019 · 1 comment · Fixed by #1477

Comments

@coreyfarrell
Copy link
Contributor

Would you be willing to have yargs re-expose yargs-parser? My hope is for nyc to be able to do something like const {Parser} = require('yargs/yargs'). This would have the benefit of guaranteeing that when nyc uses the exact same version of yargs-parser as yargs itself. It would also reduce the maintenance burden for packages like nyc, for example right now yargs-parser@16.1.0 is available but latest yargs uses yargs-parser@^15.0.0 so anyone who blindly upgrades (my CI passed so it's good) would cause two copies of yargs-parser to get installed.

@bcoe
Copy link
Member

bcoe commented Nov 9, 2019

I think this is a good idea, want to submit a patch ... we're about to release a major, so it would be a good time to land this feature.

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

Successfully merging a pull request may close this issue.

2 participants