Repository navigation
Conversation
The production build failed in next/font/google when Google Fonts returned a font URL without a file extension. Builds depended on Google being up and answering normally every time. - commit the latin variable woff2 file of each font (the same files Google serves) and load them with next/font/local - the build no longer makes any network request for fonts - output drops from 17 font files across seven subsets to 3; the site text only uses latin characters, and the latin files are the ones that were already preloaded - full-page screenshots of all four pages, desktop and mobile, light and dark, are pixel-identical to the Google Fonts build - OFL license of each font ships next to the files Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Owner
Author
|
Closing: the font failure was a transient Google Fonts hiccup; the re-run deployed fine. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maindeploy after fix(brand): serve the R/ favicon reliably and fix the manifest link #60 failed innext/font/google(Cannot read properties of null (reading '1')). Google Fonts briefly returned a font URL without a.woff2extension, which Next's loader can't parse. The same commit built fine minutes earlier, and a re-run succeeded, so every build depended on Google answering normally..woff2of each font (the exact files Google serves) and load them withnext/font/local. Builds no longer make any network request for fonts.→isn't in any subset we loaded, so it already used a fallback font), and the Latin files are the ones that were already preloaded.Verification
🤖 Generated with Claude Code