-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: support tailwindcss v4 #4656
base: beta/release-next
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (5)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
I was not able to get this to work either.
@winchesHe what are the chances of getting a beta dist-tag on npm once this is merged with the beta/release-next branch? |
Thank you for saving me time. |
…to feat/tailwindcss-v4
Once merged will release a latest beta version in npm |
tailwindlabs/tailwindcss#16664 related to |
8877be5
to
1823e5d
Compare
When I use any of these preview versions I get an runtime error:
I can confirm that this error goes away as soon as I remove the heroui content import from the tailwind config: ../../node_modules/@heroui/theme/dist/**/*.{js,ts,jsx,tsx} Using Tailwind 4.0.9, Nextjs 15.0.2 and tried both of the latest beta preview versions. I checked the implementation of the vite example and I am doing it exactly like that. |
Fixed in the latest version https://github.com/heroui-inc/heroui/runs/37994128721 |
Closes #4644
Description
The current migration is working fine with
tailwindcss js config
.It won't be released that soon because it has a lot of breaking changes.
Need to update
tailwind-merge
upgrade ✅codemod supportheroui
plugin transform tocss
fileMigration steps
https://tailwindcss.com/docs/upgrade-guide
@config "path/to/tailwindcss"
Heroui template for tailwindcss v4
heroui-inc/vite-template#10