chore: allow esbuild build scripts to fix fresh-clone install#234
chore: allow esbuild build scripts to fix fresh-clone install#234DylanPiercey wants to merge 1 commit into
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 18 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Closing — this was based on my misreading of "fresh clone". The actual issue is at the |
A fresh clone's
pnpm installfails withERR_PNPM_IGNORED_BUILDS: esbuild. esbuild is an optional peer ofvite(pulled in byvitest) and ships a postinstall that pnpm 10+ blocks by default, erroring on first install until it's approved.Whitelists it via
onlyBuiltDependenciesinpnpm-workspace.yaml(whatpnpm approve-buildswrites) so clones install cleanly.