feat: support tailwindcss v4

[winchesHe]

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

1. tailwind-merge upgrade ✅
2. codemod support heroui plugin transform to css file

Migration steps

1. Follow the official upgrade guide https://tailwindcss.com/docs/upgrade-guide
2. Install the preview version feat: support tailwindcss v4 #4656 (comment)
3. Use heroui with @config "path/to/tailwindcss"

Heroui template for tailwindcss v4

heroui-inc/vite-template#10

[changeset-bot]

⚠️ No Changeset found

Latest commit: 06a9761

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
heroui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 8, 2025 7:33pm
heroui-sb	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 8, 2025 7:33pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (5)

• main
• canary
• fix/.*
• chore/.*
• feat/.*

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[winchesHe]

tailwindlabs/tailwindcss#16664 related to ease-out important modifier issue

[christophmeise]

When I use any of these preview versions I get an runtime error:

Parsing css source code failed
  2979 |   }
  2980 |   .w-\[calc\(100\%_-_var\(spacing\.6\)\)\] {
> 2981 |     width: calc(100% - var(spacing.6));
       |                             ^
  2982 |   }
  2983 |   .w-\[calc\(2623\/16\*1rem\)\] {
  2984 |     width: calc(2623 / 16 * 1rem);

Unexpected token Ident("spacing") at [project]/apps/nextjs/src/styles/globals.css:2980:28

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}
I also removed all CSS and plugins to confirm that this is a problem with heroui.

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.

[winchesHe]

When I use any of these preview versions I get an runtime error:

Parsing css source code failed
  2979 |   }
  2980 |   .w-\[calc\(100\%_-_var\(spacing\.6\)\)\] {
> 2981 |     width: calc(100% - var(spacing.6));
       |                             ^
  2982 |   }
  2983 |   .w-\[calc\(2623\/16\*1rem\)\] {
  2984 |     width: calc(2623 / 16 * 1rem);

Unexpected token Ident("spacing") at [project]/apps/nextjs/src/styles/globals.css:2980:28

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} I also removed all CSS and plugins to confirm that this is a problem with heroui.

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

[aeltorio]

@winchesHe ,
Thank you for your impressive work.
I've updated the template React 19, TailwindCSS 4.0.9, ESLint 9, Heroui 2.7… with
https://github.com/sctg-development/vite-react-heroui-template
Thanks a lot

[Ankan002]

Does this also support nextjs?

[aeltorio]

I have synced my template to beta build.
For our needs, I have added i18n support and a simple language-switching component to change the language. This component correctly handles both LTR and RTL languages. Please note that the languages are automatically translated.

The template without i18n ends at e8d9065d36ef09c90714b099406ee6a737ef32c3

[sapjax]

I found that heroui doesn't support using-a-data-attribute as dark mode selector

@custom-variant dark (&:where([data-theme=dark], [data-theme=dark] *));

It only works with class selector:

@custom-variant dark (&:where(.dark, .dark *));