lookup: add yargs#1106
Open
wesleytodd wants to merge 1 commit into
Open
Conversation
This was referenced May 22, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1106 +/- ##
=======================================
Coverage 96.36% 96.36%
=======================================
Files 29 29
Lines 2203 2203
=======================================
Hits 2123 2123
Misses 80 80 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ljharb
approved these changes
May 22, 2026
Member
ljharb
left a comment
There was a problem hiding this comment.
good start; we should absolutely be testing yargs 16, 17, and 18 (any major that supports non-EOL nodes)
Member
|
Realistically, I do not think Yargs 18 is currently a good candidate for CITGM. The combination of no lockfile and low activity means builds can be broken for long periods: yargs/yargs#2393
|
Member
|
It's still pretty important to know when a new node release will break it - node 26 breaking yargs 16 and 17 should have delayed the release imo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Due to yargs/yargs#2509 I believe
yargsshould be in CITM.Currently it is failing because
yargsdoes not ship a lockfile and usesprettierso it pulls inprettierbreaking formatting changes intolint. I can open a PR to address this inyargsor we can excludelinthere whatever folks prefer (obviously easier to fix here).Additionally, I think the issue that occurred was on
yargs@17not18. Do we have precedent for testing multiple majors? I coudln't find any, but honestlyexpressshould have this as well until we can EOL v4. So any pointers on that would be great and I can open PRs for that.Output from `citgm yargs`
cc @bcoe @shadowspawn @nicolo-ribaudo
Checklist
npm testpasseshere