You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading from Tailwind CSS V3 to V4 and using the HeroUI plugin, I'm no longer able to access certain CSS classes such as bg-default-100 and scrollbar-hide. These classes were working fine in version 3, but now they're not being applied, and the components are not rendering as expected.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
After upgrading from Tailwind CSS V3 to V4
Expected behavior
The expected behavior is that after updating to Tailwind CSS version 4 and using the HeroUI plugin, I should still be able to use utility classes like bg-default-100 and scrollbar-hide to style my components. These classes should be properly applied, and the components should display as they did in version 3, without any issues.
Screenshots or Videos
Operating System Version
Linux (Docker)
Browser
Chrome
The text was updated successfully, but these errors were encountered:
HeroUI Version
@heroui/[email protected] @heroui/[email protected]
Describe the bug
After upgrading from Tailwind CSS V3 to V4 and using the HeroUI plugin, I'm no longer able to access certain CSS classes such as bg-default-100 and scrollbar-hide. These classes were working fine in version 3, but now they're not being applied, and the components are not rendering as expected.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
After upgrading from Tailwind CSS V3 to V4
Expected behavior
The expected behavior is that after updating to Tailwind CSS version 4 and using the HeroUI plugin, I should still be able to use utility classes like bg-default-100 and scrollbar-hide to style my components. These classes should be properly applied, and the components should display as they did in version 3, without any issues.
Screenshots or Videos
Operating System Version
Linux (Docker)
Browser
Chrome
The text was updated successfully, but these errors were encountered: