Remove experimental fontLoaders option from next.config.js (#46886 )

Currently there's an experimental option in `next.config.js` that lets you define default subset(s) to preload for all your fonts. [docs](https://nextjs.org/docs/basic-features/font-optimization#specifying-a-subset)

Over time we haven't seen much use of this option, and we are defining the subsets in the font function call in all our examples/docs. Imo it would be fine to drop this option.

This PR removes that experimental option. If you happen to use it you'll get a build error with [a link](f67af163cd/errors/google-fonts-missing-subsets.md).

Next step (breaking change for next major) would probably be to remove the preload and subsets properties from `next/font/google` calls, and just have something like [`preloadSubsets´](https://vercel.slack.com/archives/C8EAN8A94/p1674868993169559?thread_ts=1674707555.461809&cid=C8EAN8A94) that is required.

2023-03-13 21:34:43 +00:00

787 B

Raw Blame History

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.

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.

const notoSansJapanese = Noto_Sans_JP({
  weight: '400',
  preload: false,
})

Useful Links

Specifying a subset

787 B Raw Blame History

Missing specified subset for a next/font/google font