Closed irinamok closed 12 years ago
Yeah, I wonder why we are specifying such an old version of commander. Looks like commander just went 1.0 a couple of days ago, but has been up to commander 0.6 before that. Perhaps we should try updating commander. Can I take a look at this one?
Be my guest, when I specified the dependency versions in package.json I wanted to stick to at least the second decimal to avoid any surprises but definitely it'd be better if we can still work with the latest versions.
Run npm install on node 0.8.2/npm 0.1.36:
npm WARN engine commander@0.2.1: wanted: {"node":">= 0.4.x < 0.7.0"} (current: { "node":"0.8.2","npm":"1.1.36"})