Skip to content

perf(build): use node:fs for cache checks#7107

Open
43081j wants to merge 1 commit into
netlify:mainfrom
43081j:jg/the-purge-cache-globby
Open

perf(build): use node:fs for cache checks#7107
43081j wants to merge 1 commit into
netlify:mainfrom
43081j:jg/the-purge-cache-globby

Conversation

@43081j

@43081j 43081j commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

This switches from globby/cpy/etc to using the built-in node:fs functions.

We can use fs.cp to recursively copy, and fs.readdir to recursively read, so we no longer need dependencies to do this.


For us to review and ship your PR efficiently, please perform the following steps:

  • Open a bug/issue before writing your code 🧑‍💻. This ensures
    we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
    something that`s on fire 🔥 (e.g. incident related), you can skip this step.
  • Read the contribution guidelines 📖. This ensures
    your code follows our style guide and passes our tests.
  • Update or add tests (if any source code was changed or added) 🧪
  • Update or add documentation (if features were changed or added) 📝
  • Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

This switches from globby/cpy/etc to using the built-in `node:fs` functions.

We can use `fs.cp` to recursively copy, and `fs.readdir` to recursively read, so we no longer need dependencies to do
this.
@43081j 43081j requested a review from a team as a code owner June 25, 2026 13:39
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@43081j, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 41 minutes and 22 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a1a5af8e-247b-4e3b-b1be-8a85afc804a0

📥 Commits

Reviewing files that changed from the base of the PR and between 96b864c and 4f9542e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • packages/cache-utils/package.json
  • packages/cache-utils/src/fs.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@43081j 43081j changed the title perf(build): use node:fs for cache checs perf(build): use node:fs for cache checks Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant