Add documentation on Font Optimization. #24572
Merged
Conversation
This file contains 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
leerob
requested review from
divmain,
ijjk,
lfades,
shuding and
timneutkens
as code owners
ijjk
approved these changes
Apr 28, 2021
|
Great addition! I think it would be valuable to provide instructions on how to disable this optimization until #20134 gets fixed: // next.config.js
module.exports = {
optimizeFonts: false,
}; |
|
Perhaps it's just me, but for some reason, I can't see the "Font Optimization" in the navigation side bar nor on the bottom navigation "next page" and "prev page" buttons:
But it shows up when I load the page directly:
|
flybayer
pushed a commit
to blitz-js/next.js
that referenced
this pull request
Jun 1, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.