Upgrading commander from 14.x to 15.x
Comparison of the public API of commander 14.0.3 and 15.1.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 1 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 2 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed import paths
| Removed import paths |
|---|
commander/esm.mjs |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
| export | @deprecated |
|---|---|
commander · Command.storeOptionsAsProperties | since v15 |
commander · Command.combineFlagAndOptionalValue | since v15 |
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=20 | — |
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading commander from 14 to 15?
Between commander 14.0.3 and 15.1.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in commander 15?
2 exports or members are newly marked as deprecated in commander 15.1.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/commander/upgrade?from=14.0.3&to=15.1.0