To Whoever Controls the Google Font Update Github Bot

[ospira]

Link to the code that reproduces this issue

https://github.com/ospira/this-is-p/blob/main/src/app/layout.tsx#L2

To Reproduce

1. Start application
2. Do this import { Boldonse } from "next/font/google";

Current vs. Expected behavior

I expect to import my cool new font.

What I get is:

'Boldonse' is declared but its value is never read.ts(6133)
Module '"next/font/google"' has no exported member 'Boldonse'.ts(2305)

Provide environment information

n/a

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

Other (Deployed), Vercel (Deployed), next start (local), next build (local), next dev (local)

Additional context

think this is as simple as the bot that updates this got stuck. not sure since i don't run the bot (😢), but looks like the last update attempt in end of jan got stuck. i want this font plz - https://github.com/googlefonts/boldonse/ - but it's not in the latest next/font/google... cause it was recently put there and bot hasn't opened a PR since then.

here u see the last one that seems like it got stuck (https://github.com/vercel/next.js/pulls?q="Update+font+data") as usually i noticed even when a bunch are closed, one of them in a given series opened around the same date usually gets merged. so not sure, but anyway, since this seems like an auto thing, if whoever owns that could just run it again so i could get my cool new font w/o doing too much runaround work that would be peachy. thanks

[darkwaves-ofc]

Google Font Update Request for Boldonse

Hi there! I'm experiencing an issue with importing the Boldonse font from next/font/google.

Current Situation

• Attempting to import Boldonse from next/font/google
• Receiving errors:
  • 'Boldonse' is declared but its value is never read
  • Module '"next/font/google"' has no exported member 'Boldonse'

Context

• The Boldonse font is available here: https://github.com/googlefonts/boldonse/
• It seems the font update bot may have stalled (last update attempt appears to be from end of January)
• Would appreciate if the bot could be rerun to include this new font in the Next.js font library

Request

Could someone manually trigger the font data update to include Boldonse? This would help resolve the import issue without requiring manual workarounds.

Thank you for your assistance!

[MoSadie]

Any updates on this? Would love to use the new Atkinson Hyperlegible Next font but running into the same issue.
It just doesn't exist in the font data.

[MoSadie]

Not sure how to fix it but it looks like the automated update keeps failing because it is generating invalid typescript.

Looking at the latest run it seems there is a google font named 42dot Sans which generates a function named 42dot_sans which isn't valid since it starts with a numeric literal. This causes the linter to exit with a code 1 and end the automated run in a failure.

[ospira]

Not sure how to fix it but it looks like the automated update keeps failing because it is generating invalid typescript.

Looking at the latest run it seems there is a google font named 42dot Sans which generates a function named 42dot_sans which isn't valid since it starts with a numeric literal. This causes the linter to exit with a code 1 and end the automated run in a failure.

Nice look. If that's right lmk if you have any interest in pursuing a PR to fix if not I can take a crack at it over the next few days.

[MoSadie]

If you have time the PR is all yours @ospira

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.