Upgrading yargs from 17.x to 18.x
Comparison of the public API of yargs 17.7.3 and 18.2.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 | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed import paths
| Removed import paths |
|---|
yargs |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=12 | ^20.19.0 || ^22.12.0 || >=23 |
Frequently asked questions
What are the breaking changes when upgrading yargs from 17 to 18?
Between yargs 17.7.3 and 18.2.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in yargs 18?
0 exports or members are newly marked as deprecated in yargs 18.2.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/yargs/upgrade?from=17.7.3&to=18.2.0