chore: ban axios@1.14.1 via npm overrides#36
Conversation
Adds a semver range override that prevents npm from resolving axios@1.14.1 whether requested directly or transitively.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 17 minutes and 37 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 |
Extends the semver override to exclude axios@0.30.4 in addition to axios@1.14.1, both of which have known security vulnerabilities.
|



Summary
"axios": ">=0.0.0 <1.14.1 || >=1.14.2"tooverridesinpackage.jsonTest plan
npm install