next/font/google download timeout should be configurable

[carloscarnero]

Goals

1. In development mode, if I'm not mistaken, downloading a font from Google times out after 3 seconds. This value should be configurable to account for a variety of environments.

Non-Goals

No response

Background

In Next.js release v13.2.4 a timeout for the process of downloading fonts from Google Fonts was merged in #46834 for development environments. While the idea seems solid, when the network is flaky, congested, or otherwise crappy, this timeout fires too soon and fonts can't be downloaded (in fact, this has happened to me twice already.)

Proposal

The value for the timeout should be configurable, while keeping the chosen 3000 milliseconds as default. Honestly, I have no idea if the override should be set via environment variables or in next.config.js.

[carloscarnero]

@hanneslund 👋 do you think this have any merit?

[ReoHakase]

Hi dear @hanneslund

The current 3000 timeout setting is not sufficient for CJK fonts most of the time. (At least for my average network environment)
#45080 (comment)

The suggested configurable timeout would be great for DX, especially for those who develop apps in CJK languages.
Could you consider to implement the mentioned feature?

Thanks in advance

[darioscattolini]

I'm having the same issue with a regular Latin font with just two font weights, and no particular network issue: the request times out and fails. I'm not sure if making it configurable is the best solution, but at least a longer timeout could be used.

Perhaps PR #51890 solves the issue.

[absolutegravitas]

Same issue and production build fails because of it.... is this on the roadmap for "fix" anytime soon otherwise use of next/font is useless for our projects

[SC0d3r]

I am facing this issue when downloading google fonts, there should be an option to increase/set the timeout when downloading google fonts in next/font

[absolutegravitas]

Going to go back to manual script references... this package is garbage

[sneko]

@styfle @timneutkens @berlysia following your contributions to the font package (#58075 and others to retry fetching), any chance to have a configurable timeout? In my case the provider build environment I have always fails to fetch the font within the default timeout (it's a known issue, with people behind VPN...).

Thank you,

[allenchuang]

Facing this similar issue. following

[allenchuang]

bump, what is the fix here? I find myself often need to redepoly multiple times in order to get a green build.

[crobley]

bump, what is the fix here? I find myself often need to redepoly multiple times in order to get a green build.

We have the same issue running on a GitLab runner. Sometimes it's the first time, others upwards of 20 times!

[Harris-Ferguson]

Facing this issue as well, we have CI/CD builds fail pretty consistently due to this. Following.

[Luise8]

So this is still happening with github actions. I have to run many times the jobs. I'm not behind a VPN...

[zlatiz]

Running into this issue as well while using Digital Ocean App services. I have to run the CI/CD at least 10 - 15 times...

[maggie44]

It seems common in GitHub Actions when building arm64 images which require emulation. It's consumes a lot of resources so takes longer to perform actions like this, which then times out regularly.

[anthonyalayo]

Exactly my situation.

[queenvictoria]

Our use case is for a multilingual site where we consume 20+ Google fonts. The 3000ms timeout means that 9/10 development runs and 9/10 production builds fails rendering next/fonts/google unusable from a dx point of vieww. A configurable timeout would go a large distance to resolving this for us.

[mhornbacher]

Just to pile on I'm observing a fun behavior in docker where after 3 seconds it fails for all 3 retries instantly. This also occurs 100% of the time if you use a large font such as Simplified Chinese (which our app requires and is a 17MB TTF file)