build(ecdsa): remove obsolete Waffle toolchain#4168
Conversation
|
Warning Review limit reached
Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
@nomiclabs/hardhat-waffleandethereum-wafflefrom the ECDSA package, which already registers@nomicfoundation/hardhat-chai-matcherswaffle.providerusages withethers.providerand rely on the globally registered Hardhat matchersIssue #3992 proposed upgrading Waffle, but
@nomiclabs/hardhat-wafflecannot coexist with the already-loaded@nomicfoundation/hardhat-chai-matchersplugin. Removing the redundant Waffle stack completes the migration without retaining two competing Chai integrations.Validation
yarn install --immutablenpm run buildnpm run lint(passes with pre-existing warnings)npm test— 650 passing, 44 pendingnpm run deploy:testThe npm lockfile removes 1,019 package entries, adds none, and leaves every surviving package entry unchanged apart from the root dependency list. The Yarn lockfile removes 382 resolution locators and adds or upgrades none.
Lockfile overlap
Open PRs #4108, #4025, and #3904 also touch the ECDSA lockfiles and may need regeneration or a rebase after this lands. This PR intentionally includes none of their package upgrades.
Fixes #3992