fix(dev-utils): replace write-file-atomic with atomically#686
Conversation
write-file-atomic has a known issue with EPERM errors on Windows CI during atomic rename operations (npm/write-file-atomic#227). The package doesn't have retry logic and is largely unmaintained. atomically is a modern replacement that: - Retries EPERM/EBUSY/EACCES errors automatically (7.5s timeout) - Uses stubborn-fs for Windows compatibility - Has native TypeScript types (no @types package needed) - Same API surface This should fix flaky Windows CI failures in nuxt-module tests. https://claude.ai/code/session_01Am39kTSMwxUGJnbDeuJanj
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ 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 |
write-file-atomic has a known issue with EPERM errors on Windows CI during atomic rename operations (npm/write-file-atomic#227). The package doesn't have retry logic and is largely unmaintained 😬.
atomically is a modern, popular (7M downloads/wk) replacement that:
This should fix flaky Windows CI failures.
See https://npmx.dev/compare?packages=write-file-atomic,atomically.