Update Commander Dependency?

[zzen]

Any reason why commander is still at 0.3.2? There are a couple things broken. The process can terminate before help text is fully written to output (see example below).

I believe it's caused by this line in the old commander:

    jakub-air:apiary jakub$ mocha --help

      Usage: mocha [options] [files]

      Options:

        -h, --help             output usage information
        -V, --version          output the version number
        -r, --require <name>   require the given module
        -R, --reporter <name>  specify the reporter to use
        -u, --ui <name>        specify user-interface (bdd|tdd|exports)
        -g, --grep <pattern>   only run tests matching <pattern>
        -t, --timeout <ms>     set test-case timeout in milliseconds [2000]
        -s, --slow <ms>        "slow" test threshold in milliseconds [75]
        -w, --watch            watch test files for changes
        -C, --no-colors        force disabling of colors
        -c, --colors           force enabling of colors
        -G, --growl            enable growl notification support
        -S, --say [voice]      enable say notification support
        -d, --debug            enable node's debugger
        --globals <names>      allow the given comma-delimited global [names]
        --ignore-leaks         ignore global variable leaks
        --interfjakub-air:apiary jakub$ 

Also running mocha without parameters throws an error.

    Error: ENOENT, No such file or directory 'test'
        at Object.readdirSync (fs.js:376:18)
        at Object.<anonymous> (/Users/jakub/.nvm/v0.4.12/lib/node_modules/mocha/bin/_mocha:162:14)
        at Module._compile (module.js:411:26)
        at Object..js (module.js:417:10)
        at Module.load (module.js:343:31)
        at Function._load (module.js:302:12)
        at Array.<anonymous> (module.js:430:10)
        at EventEmitter._tickCallback (node.js:126:26)

[tj]

it defaults to tests in ./test, so if you run mocha that's what it's trying to find

[zzen]

Thanks for the commander update but sadly it still behaves the same. Maybe the commander needs to flush the stdout stream before process.exit()ting, not sure

[tj]

yeah I think I had a patch for that but had to revert since it introduced some other bug