♻️ Inter Font - Added preload to avoid FOUT issues #1623
Merged
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.
Relates to #1600
This pull request includes updates to replace the
@fontsource/inter
package with@fontsource-variable/inter
.@fontsource-variable/inter
version enables to use single font file that contains multiple variations of the same font, such as different weights, widths, and styles. Read more at docs - https://fontsource.org/docs/getting-started/variableAlso added
preload
option to improve performance by loading font file before they are acquired.https://fontsource.org/docs/getting-started/preload
https://web.dev/articles/codelab-preload-web-fonts
Figure: preload link was added to header
Font updates:
gatsby-browser.js
: Replaced@fontsource/inter
with@fontsource-variable/inter
.gatsby-ssr.js
: Added import for@fontsource-variable/inter
and included a preload link for thewoff2
(file that contains all font variations) font file in theonRenderBody
function.package.json
: Updated the dependency from@fontsource/inter
to@fontsource-variable/inter
.src/style.css
: Changed thefont-family
to use "Inter Variable" instead of "Inter".When refreshing the page in local, it becomes all white then the page is displayed (in production not like this). But the correct font is rendered. So I wasn't able to really test the current FOUT issue in local
Figure: Correct font is rendered in local