chore(deps): update c8 to 12.0.0#1123
Open
Renegade334 wants to merge 2 commits into
Open
Conversation
This bumps c8's yargs dependency to v18, which resolves the module resolution errors when running CI with Node.js v26.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1123 +/- ##
=======================================
Coverage 63.54% 63.54%
=======================================
Files 50 50
Lines 8507 8507
=======================================
Hits 5406 5406
Misses 3101 3101 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
This bumps c8's yargs dependency to v18, which resolves the module resolution errors when running CI with Node.js v26, and allows us to remove the package.json override.
The new package appearances in npm-shrinkwrap.json are due to other dependencies' own outdated yargs dependencies (for CLI functionality that we don't use) reappearing now that the override no longer affects them. I've separated out the two commits so as to make this clearer.