rsnext/packages/next-swc/crates
Will Binns-Smith c1217ad3e3 @next/font/google: support setting a css variable for fonts (vercel/turbo#3505)
Fixes WEB-501

Fixes https://github.com/vercel/turbo/issues/3139

This adds proper support for the [`variable`
property](https://nextjs.org/docs/api-reference/next/font#variable) when
constructing fonts. This results in:

* defining a selector in the css module for a classname defining the css
custom property (css variable), whose value is the font family
* adding a `variable` property to the resulting js object whose value is
the classname used in the selector above

Test Plan: Added an integration test.
2023-01-27 08:48:15 +01:00
..
next-binding cargo(build): expose tls for next-binding (vercel/turbo#3040) 2022-12-16 20:59:10 -08:00
next-core @next/font/google: support setting a css variable for fonts (vercel/turbo#3505) 2023-01-27 08:48:15 +01:00
next-dev Handle routing by calling Next.js code (vercel/turbo#3446) 2023-01-26 21:15:48 +01:00
next-dev-tests @next/font/google: support setting a css variable for fonts (vercel/turbo#3505) 2023-01-27 08:48:15 +01:00
next-font @next/font [2/n] Apply next/font swc transform (vercel/turbo#2742) 2022-12-05 16:09:17 -08:00
next-transform-dynamic Update mdxjs and testing crates (vercel/turbo#3398) 2023-01-20 13:47:41 -05:00
next-transform-strip-page-exports Update mdxjs and testing crates (vercel/turbo#3398) 2023-01-20 13:47:41 -05:00