-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Feature Request]Tailwind v4 support. #4644
Comments
I am facing the same problem. When is the heroui update expected? I tried this! It didn't work. hero.ts
global.css
|
You can find heroui/packages/core/theme/src/plugin.ts Line 50 in cddba82
heroui/packages/core/theme/src/plugin.ts Line 158 in cddba82
This should be easily solved. However I don't know why Tailwind CSS requests "utilities must be a single class name and start with a lowercase letter", maybe it doesn't admit pseudo-classes. According to MDN, |
Is your feature request related to a problem? Please describe.
The new version of tailwind comes with a breaking change feature to HeroUI. v4 removes the
tailwind.config.js
.This change breaks HeroUI, making the components unable to show the right style.
Describe the solution you'd like
A new version of the docs showing how we can install HeroUI with the new version of TailwindCSS.
Describe alternatives you've considered
Trying to use tailwind's way to upgrade to v3 to v4 using
With no success. It just show this error message:
Screenshots or Videos
How a Button is showing when using the new version of Tailwindcss.
The text was updated successfully, but these errors were encountered: