chore: remove transitive string.prototype.matchall polyfill#2080
chore: remove transitive string.prototype.matchall polyfill#2080gameroman wants to merge 1 commit intonpmx-dev:mainfrom
string.prototype.matchall polyfill#2080Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
string.prototype.matchall polyfillstring.prototype.matchall polyfill
📝 WalkthroughWalkthroughA pnpm workspace configuration override has been updated to include a new dependency mapping. The string.prototype.matchall package is now configured to use the no-polyfill variant version 0.0.1 from npm. The modification adds a single line to the override configuration without any other structural or logical changes. Suggested reviewers
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Revert "Remove transitive string.prototype.matchall polyfill and update lockfile" This reverts commit 26667a5. fix
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 466b3ce0-6fed-4a25-b9d5-446eb9c89c00
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
pnpm-workspace.yaml
|
Maybe using nolyfill is better indeed |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Testing my new thing
This should massively reduce dependency size without extra effort