Commander.js: Is this project maintained?

[vanesyan]

It seems there's no any active contribution since feb...

[scott-joe]

Yeah... There are 51 open PRs...

[timaschew]

and now almost one month has passed without any reaction from any maintainer

[abetomo]

Shall we fork to create a new package?

[timaschew]

I would like to know why you want to use commander and not yargs.
I switched to yargs today and I am really happy with its API.
And it's of course maintained.

Tomoaki Abe [e-mail] schrieb am Mi. 14. Juni 2017 um
17:39:

Shall we fork to create a new package?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tj/commander.js/issues/631#issuecomment-308471438,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGxFiyQ-LhGKE8TVlF8pjd4CF8BN_dNks5sD_7LgaJpZM4NbknU
.

[vanesyan]

May be we should to involve @tj into the discussion as his is the very author of the package and I'd think he also should decide want to do with the project.

[tj]

happy to add anyone who is interested in maintaining

[abetomo]

Please let me cooperate because I am indebted to commander.js.

[vanesyan]

I'd also like to help out with maintaining the project. :)

[tj]

added you both :D just let me know what your npm usernames are

[abetomo]

Thank you. I am the same as github.

[vanesyan]

Awesome :) @vanesyan on npm too

[tj]

done!

[vanesyan]

Awesome!

[zhiyelee]

nice

[vanesyan]

A bunch of new maintainers been added, so close it for now