Conversation
- Replace npm publish with bun publish using NPM_CONFIG_TOKEN - Add files field to package.json to scope published contents - Remove unnecessary .npmrc creation step Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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
npm publishwithbun publishto fixCannot read properties of null (reading 'matches')errorfilesfield topackages/chronicle/package.jsonto explicitly scope published contents.npmrccreation step;bun publishusesNPM_CONFIG_TOKENenv var directlyTest plan
bun publish --dry-runlocally (117 files, 0.48MB)🤖 Generated with Claude Code