salsita
fix(deps): update dependency yargs to v18
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| yargs (source) | ~17.7.0 -> ~18.0.0 |
Release Notes
yargs/yargs (yargs)
v18.0.0
⚠ BREAKING CHANGES
- command names are not derived from modules passed to
command. - singleton usage of yargs yargs.foo, yargs().argv, has been removed.
- minimum node.js versions now
^20.19.0 || ^22.12.0 || >=23. - yargs is now ESM first
Features
- commandDir now works with ESM files (#2461) (27eec18)
- locale: adds hebrew translation (#2357) (4266485)
- yargs is now ESM first (d90af45)
- zsh: Add default completion as fallback (#2331) (e02c91b)
Bug Fixes
- addDirectory do not support absolute command dir (#2465) (3a40a78)
- allows ESM modules commands to be extensible using visit option (#2468) (200e1aa)
- browser: fix shims so that yargs continues working in browser context (#2457) (4ae5f57)
- build: address problems with typescript compilation (#2445) (8d72fb3)
- coerce should play well with parser configuration (#2308) (8343c66)
- deps: update dependency yargs-parser to v22 (#2470) (639130d)
- exit after async handler done (#2313) (e326cde)
- handle spaces in bash completion (#2452) (83b7788)
- parser-configuration should work well with generated completion script (#2332) (888db19)
- propagate Dictionary including undefined in value type (#2393) (2b2f7f5)
- zsh: completion no longer requires double tab when using autoloaded (0dd8fe4)
Code Refactoring
- command names are not derived from modules passed to
command. (d90af45) - singleton usage of yargs yargs.foo, yargs().argv, has been removed. (d90af45)
Build System
- minimum node.js versions now
^20.19.0 || ^22.12.0 || >=23. (d90af45)
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
Coverage Report
| Status | Category | Percentage | Covered / Total |
|---|---|---|---|
| 🟢 | Lines | 92.53% (🎯 90%) 🟰 ±0% | 3273 / 3537 |
| 🟢 | Statements | 92.53% (🎯 90%) 🟰 ±0% | 3273 / 3537 |
| 🟢 | Functions | 96.7% (🎯 90%) 🟰 ±0% | 264 / 273 |
| 🟢 | Branches | 91.15% (🎯 85%) 🟰 ±0% | 866 / 950 |
File Coverage
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@brenoepics do you think we can safely upgrade to v18? can this have any downside effects for consumers?
@brenoepics do you think we can safely upgrade to v18? can this have any downside effects for consumers?
Hmm. we're ESM-only so the ESM-first change isn't an issue.
We're not using any of the deprecated patterns like yargs.argv, yargs.foo, or command() / commandDir(), so none of the major breaking changes really affect us.
v18 requires Node ^20.19.0, our current minimum is >=20.11.0, should we just bump it to >=20.19.0 to match?
We're not doing anything fancy with yargs anyway, so this should be a pretty smooth upgrade, I tried it locally while taking a look at some issues and seems fine.
@brenoepics do you think we can safely upgrade to v18? can this have any downside effects for consumers?
Hmm. we're ESM-only so the ESM-first change isn't an issue. We're not using any of the deprecated patterns like
yargs.argv,yargs.foo, orcommand()/commandDir(), so none of the major breaking changes really affect us. v18 requires Node^20.19.0, our current minimum is>=20.11.0, should we just bump it to>=20.19.0to match? We're not doing anything fancy withyargsanyway, so this should be a pretty smooth upgrade, I tried it locally while taking a look at some issues and seems fine.
That's a great sanity check 💚