update & fix dependencies

[alexlamsl]

No description provided.

[XhmikosR]

Why did you lock commander to 2.20.0 @alexlamsl?

[alexlamsl]

Because 2.20.1 was causing Travis CI to fail, and they don't plan on updating 2.x any further.

[XhmikosR]

I don't see how this can be true. They didn't touch the dependencies, only devDependencies.

tj/commander.js@v2.20.0...v2.20.1

[L2jLiga]

@XhmikosR they change {} with Set which is not supported by node.js 0.10, node 0.10 specified in .travis.yml and that causing CI to fail

[XhmikosR]

Right. I couldn't even imagine there would be someone still supporting Node.js 0.10.

[XhmikosR]

@alexlamsl please change back to a semver range to allow package managers to flatten the deps tree. commander 2.20.3 is out which revert the Set change.

But you should drop 0.10 support. It's 2019.

[alexlamsl]

@XhmikosR thanks for the heads up - will test and update.

And it's not the first time you and I have fundamental differences on the concept of compatibility, so thanks again for your opinion but Node.js 0.10 is here to stay.