Hannes Bornö cb729c1087 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
..
_app.js	Remove experimental fontLoaders option from next.config.js (#46886)	2023-03-13 21:34:43 +00:00
font-without-preloadable-subsets.js	Add next/font import (#45891)	2023-02-16 15:33:39 +01:00
variable-font-without-weight-range.js	Remove experimental fontLoaders option from next.config.js (#46886)	2023-03-13 21:34:43 +00:00
variables.js	Remove experimental fontLoaders option from next.config.js (#46886)	2023-03-13 21:34:43 +00:00
with-fallback.js	Remove experimental fontLoaders option from next.config.js (#46886)	2023-03-13 21:34:43 +00:00
with-fonts.js	Add support for font loaders (#40746)	2022-09-21 22:12:59 -07:00
with-google-fonts.js	Remove experimental fontLoaders option from next.config.js (#46886)	2023-03-13 21:34:43 +00:00
with-local-fonts.js	Add next/font import (#45891)	2023-02-16 15:33:39 +01:00
without-fonts.js	Add support for font loaders (#40746)	2022-09-21 22:12:59 -07:00