rsnext/errors/google-fonts-missing-subsets.md
Hannes Bornö e64bf98511
Update font links and add missing error (#41910)
Adds an error that was missing. Link to beta until the changes are live.

closes #41900

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have a helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
2022-10-26 23:00:40 -07:00

727 B

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.

  • On a font per font basis by adding it to the function call
const inter = Inter({ subsets: ['latin'] })
  • Globally for all your fonts
// next.config.js
module.exports = {
  experimental: {
    fontLoaders: [
      { loader: '@next/font/google', options: { subsets: ['latin'] } },
    ],
  },
}

If both are configured, the subset in the function call is used.

Specifying a subset