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

feat: Bump TailwindCSS to Version 4 #2053

Open
elianrichard opened this issue Feb 4, 2025 · 2 comments · May be fixed by #2056
Open

feat: Bump TailwindCSS to Version 4 #2053

elianrichard opened this issue Feb 4, 2025 · 2 comments · May be fixed by #2056
Labels
🌟 enhancement New feature or request

Comments

@elianrichard
Copy link

Is your feature request related to a problem? Please describe.

I think it would be great to implement the new Tailwind version 4 in the T3 stacks. I'm a bit frustrated when I'm required to migrate the Tailwind from version 3 to version 4 every time I uses the T3 stacks.

Describe the solution you'd like to see

  • Bump Tailwind version into version 4 in package.json file
  • Delete the tailwind.config.ts file
  • Adjust the global.css file to have the new @theme attribute and replaces the old @tailwind directives into @import tailwindcss

More about this: https://tailwindcss.com/docs/upgrade-guide

Describe alternate solutions

The user probably can choose which version of Tailwind they would like to use when initializing the T3 stacks through the CLI

Additional information

No response

@elianrichard elianrichard added the 🌟 enhancement New feature or request label Feb 4, 2025
@FleetAdmiralJakob
Copy link

I prefer leaving the config file as I dislike my typesafe code being replaced by CSS. You can do this with the new @config directive

@elianrichard elianrichard linked a pull request Feb 7, 2025 that will close this issue
3 tasks
@Kulimeya
Copy link

Kulimeya commented Feb 8, 2025

In the meantime you can use the official upgrader: npx @tailwindcss/upgrade@next

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌟 enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants