2.2.0 isn't compatible any more with parseInt used with default arguments

[kornelski]

 require('commander').
 option('--port <num>', 'Port number to listen on', parseInt, 9000).
 parse([ 'node', 'main.js', '--port=80' ]).
 port

This works as expected in 2.1.0, but in 2.2.0 parseInt is given 9000 as a second argument, which makes it output nonsense.

[rymai]

I ran across this issue too. I've worked around (temporarily I hope) it like this:

function myParseInt(string, defaultValue) {
  var int = parseInt(string, 10);

  if (typeof int == 'number') {
    return int;
  } else {
    return defaultValue;
  }
}

and then:

 require('commander').
 option('--port <num>', 'Port number to listen on', myParseInt, 9000).
 parse([ 'node', 'main.js', '--port=80' ]).
 port

[oliverzy]

Me too. I think maybe it should be mentioned in doc at least. It took me half hour to figure out what happened.

[hildjj]

At a minimum, the README must be fixed. The examples in it do not run anymore, because:

parseInt("6", 2)

yields NaN. The second parameter to parseInt is all about the base.

[zhiyelee]

I have edited the History.md in 863e73a

[shadowspawn]

Oops, used this as the earliest report and want it open as I am linking to it from multiple places!

[shadowspawn]

I have proposed a large update to options coverages in README in #953

[shadowspawn]

The options coverage in the README has been updated and includes new description of custom option processing, including a working parseInt example.

https://github.com/tj/commander.js#custom-option-processing