| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sorry, something went wrong.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting. Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
Walkthroughnuxt.config.ts updates "Geist" and "Geist Mono" font entries to use provider: 'local', numeric weights (Geist: [400, 500, 600]; Geist Mono: [400, 500]), retains global: true, and removes prior preload settings. ChangesGeist Font Configuration
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. ❤️ ShareComment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
There was a problem hiding this comment.
Why ttf, and why not the npm provider?
Sorry, something went wrong.
There was a problem hiding this comment.
Hmm, I don't see much reasons in adding a package. It seems like the font should remain unchanged (and auto package updates could also break in this case)
But honestly, these fonts simply already existed. We even used them before due to the specifics of previous og generation (now only for storybook)
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Sorry, something went wrong.
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)nuxt.config.ts (1)276-315: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win
Local provider should resolve Geist/Geist Mono without src; review IBM Plex provider consistency.
provider: 'local' without src is aligned with @nuxt/fonts’ local provider behaviour (auto-discovery from public/ with filename-derived weight/style). This repo contains public/fonts/Geist-{Regular,Medium,SemiBold}.ttf (400/500/600) and public/fonts/GeistMono-{Regular,Medium,Bold}.ttf (400/500), so the configured Geist/Geist Mono entries should resolve correctly.
IBM Plex Sans Arabic still lacks provider: 'local' (and keeps weights: ['400','500','600']), so it may continue using the default/remote provider. If the intent is to keep this fully local, set provider: 'local' and ensure matching IBM Plex font files exist and follow the expected naming convention.
🤖 Prompt for AI AgentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@nuxt.config.ts` around lines 276 - 315, The font families block defines Geist and Geist Mono correctly using provider: 'local' and should resolve to public/fonts/Geist-{Regular,Medium,SemiBold}.ttf and public/fonts/GeistMono-{Regular,Medium,Bold}.ttf, but the "IBM Plex Sans Arabic" entry is missing provider: 'local' and will fall back to a remote provider; add provider: 'local' to the "IBM Plex Sans Arabic" family entry in the families array (and keep weights: ['400','500','600']) and ensure matching font files exist in public/fonts following the `@nuxt/fonts` local naming convention (e.g. IBMPlexSansArabic-{WeightName}.ttf) so the local provider can auto-discover them.
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@nuxt.config.ts`:
- Around line 276-315: The font families block defines Geist and Geist Mono
correctly using provider: 'local' and should resolve to
public/fonts/Geist-{Regular,Medium,SemiBold}.ttf and
public/fonts/GeistMono-{Regular,Medium,Bold}.ttf, but the "IBM Plex Sans Arabic"
entry is missing provider: 'local' and will fall back to a remote provider; add
provider: 'local' to the "IBM Plex Sans Arabic" family entry in the families
array (and keep weights: ['400','500','600']) and ensure matching font files
exist in public/fonts following the `@nuxt/fonts` local naming convention (e.g.
IBMPlexSansArabic-{WeightName}.ttf) so the local provider can auto-discover
them.
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: b6f04d1e-06b4-4d09-9fd6-46da762a25a2
📥 CommitsReviewing files that changed from the base of the PR and between e9b15e5 and a2dd9cd.
📒 Files selected for processing (1)
Sorry, something went wrong.
There was a problem hiding this comment.
nuxt.config.ts (1)🤖 Prompt for all review comments with AI agents284-289: ⚡ Quick win
Harmonise weights types for discrete font weights
@nuxt/fonts supports weights as numeric arrays and also string forms (commonly for variable-range syntax like '100 900'), so the current numbers-vs-strings mix is likely acceptable. For discrete weights though, keeping the representation consistent improves readability/maintainability—use number weights for “IBM Plex Sans Arabic” to match Geist.
♻️ Suggested fix🤖 Prompt for AI Agents{ name: 'IBM Plex Sans Arabic', weights: [400, 500, 600], global: true, subsets: ['arabic'], }Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@nuxt.config.ts` around lines 284 - 289, The fonts entry uses mixed types for discrete font weights—update the "IBM Plex Sans Arabic" font configuration to use numeric weights (e.g., change any string weight entries to numbers like 400, 500, 600) to match the "Geist" entry and improve consistency; locate the IBM Plex Sans Arabic object in nuxt.config.ts (the font entry with name "IBM Plex Sans Arabic", provider, subsets/global keys) and replace the weights array with numeric values such as [400, 500, 600].
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Nitpick comments: In `@nuxt.config.ts`: - Around line 284-289: The fonts entry uses mixed types for discrete font weights—update the "IBM Plex Sans Arabic" font configuration to use numeric weights (e.g., change any string weight entries to numbers like 400, 500, 600) to match the "Geist" entry and improve consistency; locate the IBM Plex Sans Arabic object in nuxt.config.ts (the font entry with name "IBM Plex Sans Arabic", provider, subsets/global keys) and replace the weights array with numeric values such as [400, 500, 600].
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: eba65189-dbbe-4b47-87fe-ead44bded182
📥 CommitsReviewing files that changed from the base of the PR and between a2dd9cd and 372f0aa.
📒 Files selected for processing (1)
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)nuxt.config.ts (1)🤖 Prompt for all review comments with AI agents280-291: 💤 Low value
Consider standardising weight values to numeric arrays.
The font configurations use inconsistent weight value types:
- Lines 280, 286: Numeric arrays ([400, 500, 600], [400, 500])
- Line 291: String array (['400', '500', '600'])
For better type consistency and to follow TypeScript best practices, consider standardising all font weight arrays to use the same type (preferably numeric).
♻️ Suggested standardisation🤖 Prompt for AI Agents{ name: 'IBM Plex Sans Arabic', - weights: ['400', '500', '600'], + weights: [400, 500, 600], global: true, subsets: ['arabic'], },Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@nuxt.config.ts` around lines 280 - 291, The font config for "IBM Plex Sans Arabic" uses string weight values while others use numbers—standardise all font weight arrays to numeric types (e.g., change weights: ['400','500','600'] to weights: [400, 500, 600]) to ensure consistent typing; update the weights entry on the "IBM Plex Sans Arabic" object and verify other font objects like "Geist Mono" and the first font block use numeric arrays so TypeScript types for the font config remain uniform.
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Inline comments: In `@nuxt.config.ts`: - Line 286: Update the Nuxt fonts configuration for the Geist Mono entry: replace the incorrect property name "weight" with the correct "weights" and set it to the same array [400, 500]; locate the Geist Mono font block in nuxt config (search for "Geist Mono" or the fonts module configuration and the "weight" key) and change weight: [400, 500] to weights: [400, 500] so the `@nuxt/fonts` module will register and load the specified font weights. --- Nitpick comments: In `@nuxt.config.ts`: - Around line 280-291: The font config for "IBM Plex Sans Arabic" uses string weight values while others use numbers—standardise all font weight arrays to numeric types (e.g., change weights: ['400','500','600'] to weights: [400, 500, 600]) to ensure consistent typing; update the weights entry on the "IBM Plex Sans Arabic" object and verify other font objects like "Geist Mono" and the first font block use numeric arrays so TypeScript types for the font config remain uniform.
Fix all unresolved CodeRabbit comments on this PR:
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 4b0003b2-6524-4197-9d1d-2226d19b3c92
📥 CommitsReviewing files that changed from the base of the PR and between 372f0aa and 79cba81.
📒 Files selected for processing (1)
Sorry, something went wrong.
| { | ||
| name: 'Geist Mono', | ||
| weights: ['400', '500'], | ||
| preload: true, |
There was a problem hiding this comment.
are we deliberately disabling preload?
Sorry, something went wrong.
Sorry, something went wrong.
Co-authored-by: Daniel Roe <daniel@roe.dev>
Co-authored-by: Daniel Roe <daniel@roe.dev>
| Back | FazBrowse Home | New Git URL |
🧭 Context
The Geist Mono font recently broke. Because of this, ligatures (-->, ==, !=, ..., --, etc.) no longer displayed correctly. This has already been fixed - google/fonts#10540 - but due to several other services and caching issues font continues to be broken.
📚 Description
I used local fonts, as they are already configured in our repository. This will be more stable and should not impact performance overall, as users connect to our servers and wit ha few locations