Self-host Geist fonts to fix local Next.js startup#1149
Conversation
|
Warning Review limit reached
Next review available in: 32 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ 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 |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #4763 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 similar comment
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
…rtup-failure-and-verify-pages
Gate the Differentials hero composer slot so a typed draft with leftover evidence matches stays on the phone dock path, and drop the duplicated PR #1149 branch-review ledger row blocking Static PR checks. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Fixes Codex P1 check-branch-review-ledger failure on this branch. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
* Fix React hydration mismatches and add Playwright safeguards * Fix typescript and knip CI failures * fix: harden hydration guard Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix: format hydration support files Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix: harden hydration warning guard Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * docs: record Run PR behind-main sweep for #1131 * fix: sync theme cookie with bootstrap and useTheme RootLayout already reads clinical-theme for the html class, but the pre-paint bootstrap and setter only used localStorage. Fall back to the cookie in bootstrap, write/clear it from useTheme, and share the key constants so a cookie-only preference no longer flips after paint. * docs: ledger Run PR babysit for #1131 * docs: ledger post-main sync for #1131 * fix(hydration): drop suppressHydrationWarning from skip link The lint rule only allows suppressHydrationWarning on html/body/script. Remove it from the skip-to-content anchor so Static PR checks pass. * docs: ledger re-sync sweep for PR #1131 * fix(ledger): remove duplicate PR #1149 row after main merge Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix(ci): remove duplicate hydration ledger row * fix(ui): drop unused LoadingPanel import after lazy-module merge Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * test(ui): cover persisted hydration state * docs: record PR 1131 hydration coverage --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Merge from main cloned an identical #1149 review record; keep the first occurrence so check:branch-review-ledger passes.
2 participants
Motivation
next/font/googleattempted to fetch Google-hosted Geist font files during build/dev time in restricted/networked environments, so the app must avoid external font fetches while keeping typography visually equivalent.Description
next/font/googlewithnext/font/localinsrc/app/layout.tsxand point the sans/mono faces at the bundled Geist.woff2files undernode_modules/next/dist/next-devtools/server/font/.--font-geist-sans,--font-geist-mono),display: "swap", and the monopreload: falsebehaviour so visual typography remains as close as practical.src/app/layout.tsxonly.Testing
npm run ensureand confirmed the dev server previously failed due to Google font fetches and now starts successfully at the local URL after the change.npm run typecheckandnpm run check:runtime, both passed; HTTP smoke checks for the Services pages usingcurlalso returned expected content.npm run verify:ui, which completed the app build successfully but automated Chromium browser tests could not run becausenpx playwright install chromiumfailed due to a blocked download (cdn.playwright.devreturned HTTP 403), so full browser test execution is environment-blocked.Codex Task