mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
74a19b7467
## Summary Remove redundant `#` from [error pages](https://github.com/vercel/next.js/tree/canary/errors). ## Description Follow up #52038 and #72263. Updated [template.txt](https://github.com/vercel/next.js/blob/canary/errors/template.txt) and clarified the header deps. Then rewrite as per the template. ### Improving Documentation - [x] Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide Co-authored-by: Delba de Oliveira <[email protected]>
33 lines
835 B
Plaintext
33 lines
835 B
Plaintext
---
|
|
title: 'Missing specified subset for a `next/font/google` font'
|
|
---
|
|
|
|
## Why This Error Occurred
|
|
|
|
Preload is enabled for a font that is missing a specified subset.
|
|
|
|
## Possible Ways to Fix It
|
|
|
|
### Specify which subsets to preload for that font.
|
|
|
|
```js filename="example.js"
|
|
const inter = Inter({ subsets: ['latin'] })
|
|
```
|
|
|
|
Note: previously it was possible to specify default subsets in your `next.config.js` with the `experimental.fontLoaders` option, but this is no longer supported.
|
|
|
|
### Disable preloading for that font
|
|
|
|
If it's not possible to preload your intended subset you can disable preloading.
|
|
|
|
```js filename="example.js"
|
|
const notoSansJapanese = Noto_Sans_JP({
|
|
weight: '400',
|
|
preload: false,
|
|
})
|
|
```
|
|
|
|
## Useful Links
|
|
|
|
[Specifying a subset](/docs/pages/building-your-application/optimizing/fonts#specifying-a-subset)
|