Upgrading yargs-parser from 21.x to 22.x
Comparison of the public API of yargs-parser 21.1.1 and 22.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| 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 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 |
Changelog between these versions
Text published by the package authors, shown as-is.
22.0.0
### ⚠ BREAKING CHANGES
* yargs is now ESM first ([#503](https://github.com/yargs/yargs-parser/issues/503))
### Features
* yargs is now ESM first ([#503](https://github.com/yargs/yargs-parser/issues/503)) ([6d69295](https://github.com/yargs/yargs-parser/commit/6d692953ade099375c6c5e131367968b07ae8470))Frequently asked questions
What are the breaking changes when upgrading yargs-parser from 21 to 22?
Between yargs-parser 21.1.1 and 22.0.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in yargs-parser 22?
0 exports or members are newly marked as deprecated in yargs-parser 22.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/yargs-parser/upgrade?from=21.1.1&to=22.0.0