cb729c1087
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.
30 lines
634 B
TypeScript
30 lines
634 B
TypeScript
export type AdjustFontFallback = {
|
|
fallbackFont: string
|
|
ascentOverride?: string
|
|
descentOverride?: string
|
|
lineGapOverride?: string
|
|
sizeAdjust?: string
|
|
}
|
|
|
|
export type FontLoader = (options: {
|
|
functionName: string
|
|
variableName: string
|
|
data: any[]
|
|
emitFontFile: (
|
|
content: Buffer,
|
|
ext: string,
|
|
preload: boolean,
|
|
isUsingSizeAdjust?: boolean
|
|
) => string
|
|
resolve: (src: string) => string
|
|
isDev: boolean
|
|
isServer: boolean
|
|
loaderContext: any
|
|
}) => Promise<{
|
|
css: string
|
|
fallbackFonts?: string[]
|
|
variable?: string
|
|
adjustFontFallback?: AdjustFontFallback
|
|
weight?: string
|
|
style?: string
|
|
}>
|