Skip to content

Fix Node 24 Playwright install hang#4

Merged
ogrodev merged 1 commit into
mainfrom
fix-node24-playwright-install
May 31, 2026
Merged

Fix Node 24 Playwright install hang#4
ogrodev merged 1 commit into
mainfrom
fix-node24-playwright-install

Conversation

@ogrodev
Copy link
Copy Markdown
Owner

@ogrodev ogrodev commented May 31, 2026

Summary

  • restore Node 24 to the Next.js integration matrix
  • install Playwright browsers under Node 22, then switch to the matrix Node version before running the test
  • use the local Playwright CLI via npx --no-install and cap browser installation to 5 minutes so stale downloads fail fast instead of blocking the workflow

Why

The stale Node 24 runs were not failing in the app or tests. They hung in the Playwright browser install step after the Chromium archive reached 100% downloaded. Node 20 and Node 22 completed the same install path; installing the browser under Node 22 avoids the installer hang while still running the integration test under Node 24.

Verification

  • npx --no-install playwright --version
  • npx --no-install playwright install --with-deps --only-shell --dry-run chromium
  • bun run test:playwright

@vercel
Copy link
Copy Markdown

vercel Bot commented May 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tyndale-website Ready Ready Preview, Comment May 31, 2026 1:17pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 31, 2026

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

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

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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c5de023f-f11b-49db-bee2-d37d37b6a574

📥 Commits

Reviewing files that changed from the base of the PR and between 40772d2 and acbc91b.

📒 Files selected for processing (1)
  • .github/workflows/portability.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-node24-playwright-install

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 and usage tips.

@ogrodev ogrodev merged commit e0b1476 into main May 31, 2026
17 checks passed
@ogrodev ogrodev deleted the fix-node24-playwright-install branch May 31, 2026 13:28
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