ThomasCrevoisier/psvm-js

Does not parse arguments on ubuntu linux

Closed this issue · 4 comments

I've made a fix, posted a pull request at cliparse-node, but it does not seem very active.

CleverCloud/cliparse-node#19

Also tested locally, and it works for me, on my machine ;-).

I hope the pull request gets merged, but not too optimistic (a few others in the queue there).

thanks for tracking this down! This affected me too, but I couldn't work out what was going on. It might also be worth considering switching to a more popular package for getting command line arguments, such as yargs?

I've sent the mainainer an e-mail, maybe I'll get some more info about the
status of it. I'll also ask a friend who lives locally and is probably
active in the same communities.

I tracked it down after hesitating at least three times (I'd prefer Stack
for Purescript, but can't afford to build it anytime soon). Change was
surprisingly easy to make, thanks to the issue I found describing the
location already. Test suite is not too bad either, so I'm moderately
confident it didn't break e.g. the windows version.

Upsides of switching:

  • better maintained

Downsides of switching

  • rewrite costs time and effort
  • well maintained may mean more time spent on breaking things because the
    API changes and its not that important.

On Tue, Jun 28, 2016 at 5:13 PM, Harry Garrood notifications@github.com
wrote:

thanks for tracking this down! This affected me too, but I couldn't work
out what was going on. It might also be worth considering switching to a
more popular package for getting command line arguments, such as yargs
https://github.com/yargs/yargs?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAK7uJsupZIxHXA9xHF0pAZq8AX6_O-pks5qQUgagaJpZM4JARJW
.

Direct e-mail helped, pull request will be merged soon :-).

On Wed, Jun 29, 2016 at 2:14 PM, Willem van den Ende <
willem@livingsoftware.nl> wrote:

I've sent the mainainer an e-mail, maybe I'll get some more info about the
status of it. I'll also ask a friend who lives locally and is probably
active in the same communities.

I tracked it down after hesitating at least three times (I'd prefer Stack
for Purescript, but can't afford to build it anytime soon). Change was
surprisingly easy to make, thanks to the issue I found describing the
location already. Test suite is not too bad either, so I'm moderately
confident it didn't break e.g. the windows version.

Upsides of switching:

  • better maintained

Downsides of switching

  • rewrite costs time and effort
  • well maintained may mean more time spent on breaking things because the
    API changes and its not that important.

On Tue, Jun 28, 2016 at 5:13 PM, Harry Garrood notifications@github.com
wrote:

thanks for tracking this down! This affected me too, but I couldn't work
out what was going on. It might also be worth considering switching to a
more popular package for getting command line arguments, such as yargs
https://github.com/yargs/yargs?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAK7uJsupZIxHXA9xHF0pAZq8AX6_O-pks5qQUgagaJpZM4JARJW
.

Thanks a lot for the report :)

I keep using cliparse-node when I want to do a cli with subcommands as it is quite simple, I should probably take a look at yargs and other solutions for curiosity though :)