fix: strict align config and ignore behavior - #6
Conversation
|
Warning Review limit reached
Next review available in: 26 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 Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds cache-bypassing fresh module loading to ChangesCore feature changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/config-file.ts`:
- Around line 92-125: The cache-bypass logic in importNativeFreshModule and
requireFreshModule only refreshes the top-level config file, so imported helper
modules can still stay stale. Update the config loading flow used by
getFreshImportCacheKey, importNativeFreshModule, and requireFreshModule so that
useCache: false also bypasses cached dependencies: for CommonJS, clear the full
require dependency chain, and for native ESM, ensure child imports get
cache-busting treatment or are reloaded through the same fresh-import path.
- Around line 154-166: In importFreshJavaScriptConfigModule, the bare catch is
retrying all requireFreshModule failures, including config evaluation errors,
which can re-run a broken CommonJS config through importNativeFreshModule and
importJitiConfigModule. Narrow the fallback so it only catches loader/interop
compatibility cases from requireFreshModule, and rethrow ordinary execution
errors immediately. Keep the existing module detection and fallback flow, but
distinguish the failure type before deciding whether to retry.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d2e3bf2e-151f-4b66-aeb6-2aa078be694b
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (17)
.agents/skills/bump-oxfmt/SKILL.md.agents/skills/bump-oxfmt/agents/openai.yaml.github/workflows/autofix.yml.github/workflows/ci.yml.github/workflows/release.yml.oxlintrc.jsonc.vscode/settings.jsonREADME.mdpackage.jsonsrc/config-file.tssrc/constants.tssrc/core.tssrc/editorconfig.tssrc/ignore.tssrc/types.tstests/load-config.test.tstests/resolve-ignore.test.ts
Summary by CodeRabbit
New Features
Bug Fixes
Documentation