Last 12 weeks · 7 commits
4 of 6 standards met
It seems like the version option is always treated as an error (as all calls to are), even though it is successful. Whilst I understand that using a callback means that it can be handled appropriately, surely the callback shouldn't be receiving a if it isn't always going to be an error? Version option calling with status 0 always using
Repository: tj/commander.js. Description: node.js command-line interfaces made easy Stars: 27977, Forks: 1745. Primary language: JavaScript. Languages: JavaScript (95.5%), TypeScript (4.5%). License: MIT. Latest release: v14.0.3 (1mo ago). Open PRs: 2, open issues: 10. Last activity: 4d ago. Community health: 85%. Top contributors: shadowspawn, tj, zhiyelee, dependabot[bot], abetomo, SomeKittens, aweebit, thethomaseffect, tonylukasavage, mojavelinux and others.
The big changes in Commander 15 are: switching from CommonJS implementation to ESM implementation requiring Node.js v22.12.0 or higher A prerelease is available now. See the release notes for all the details: https://github.com/tj/commander.js/releases/tag/v15.0.0-0 The release of Commander 15.0.0 will be in May 2026, after Node.js 20 goes EOL.
Problem I put in as a placeholder for the Commander version in the example packages, but that does not work with the prerelease. Solution Now we have a prerelease, use that. (I could have done this in advance but didn't work it out at the time!)