Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v4] font family config breaks in 4.0.0-alpha.32 #14985

Closed
F-fengzi opened this issue Nov 13, 2024 · 4 comments
Closed

[v4] font family config breaks in 4.0.0-alpha.32 #14985

F-fengzi opened this issue Nov 13, 2024 · 4 comments

Comments

@F-fengzi
Copy link

What version of Tailwind CSS are you using?

v4.0.0-alpha.33

What build tool (or framework if it abstracts the build tool) are you using?

vite 5.4.11, @tailwindcss/vite 4.0.0-alpha.33, svelte 5.4.16

What version of Node.js are you using?

v20.17.0

What browser are you using?

Chrome 130

What operating system are you using?

Windows

Reproduction URL

https://play.tailwindcss.com/8JDdWlTAd5

Describe your issue

Custom font family config in @theme stops working at 4.0.0-alpha.32. Confirmed working in 4.0.0-alpha.31.

Elements fell back to the default font. The expected behavior is to use the font family defined in @theme.
Successfully reproduced the issue in the above Playground url. To reproduce yourself, use Tailwind 4.0.0-alpha.32 and configure a custom font family.

@philipp-spiess
Copy link
Member

@F-fengzi Hey! This is actually a change that we've made to the --font-family variable. It's now called --font only: #14885

We somehow forgot about adding this to the changelog though, I will add this right away. Sorry for the troubles.

@F-fengzi
Copy link
Author

Oh 😅! That makes more sense, you guys did change a lot in 32.

Thanks! Hopefully this helps future people too.

@philipp-spiess
Copy link
Member

philipp-spiess commented Nov 13, 2024

you guys did change a lot in 32

Getting ready for a beta release very soon 🤞 After that the API will be a lot more stable*

(* although we still might make changes before the official release, no guarantees haha)

@F-fengzi
Copy link
Author

Coooool, excited for it :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants