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

Use yargs #1180

Merged
merged 1 commit into from Mar 12, 2016
Merged

Use yargs #1180

merged 1 commit into from Mar 12, 2016

Conversation

TrySound
Copy link
Contributor

Fix #1179

kpdecker added a commit that referenced this pull request Mar 12, 2016
@kpdecker kpdecker merged commit 6b64480 into handlebars-lang:master Mar 12, 2016
nknapp pushed a commit that referenced this pull request Mar 9, 2017
In yargs 3.2, any non-truthy return value to check will fail: https://github.com/yargs/yargs/blob/master/CHANGELOG.md#302-20150213-1650-0000
It appears that this check is no longer necessary as the other contents of the check callback no longer exist: 2e7a3bd#diff-2aff13863648736946e83d70c5e63520L86
It appears the build failed for PR #1180, not sure why it was merged
@webmaster128
Copy link

hi all and thanks for making handlebars!

I see this more than 3 year old patch but I still have optimist in my dependencies. Did this not make it into the 4.x release at all?

@nknapp
Copy link
Collaborator

nknapp commented Nov 15, 2019

No, @wycats wants a spec before adding new features (#1277) so I am currently only fixing bugs, security issues and make improvements to the build-environment and code cleansiness...

I'm not sure if any compability issues arise by using yargs, so I'll not add it in 4.x.

I'm trying to move development back to the master-branch, so I may attempt to release 5.0 with the changes on master (#1566) . But I am in no rush.

Is there are particular reason why you ask about this?

@webmaster128
Copy link

Is there are particular reason why you ask about this?

I just found this super old dependency in my tree

wordwrap@~0.0.2:
  version "0.0.3"

which happens to be pulled in by

optimist@^0.6.1:
  version "0.6.1"

which appears to be unmaintained for 6 years. My feeling was those should not be in my dependency tree these days. Then I found #1179 and this PR, which were closed/merged so long ago.

So yeah, no strictly required but it would be a nice cleanup

@serhiyzablotskiy
Copy link

I also have optimist in dependencies of handlebars@4.7.3. And now it has vulnerability with minimist.
Screen Shot 2020-03-27 at 4 39 16 PM

@webmaster128
Copy link

@serhiyzablotskiy see #1662 for the latest discussion on that topic

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

Successfully merging this pull request may close these issues.

Optimist is deprecated
5 participants