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.

Sign up for GitHub

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

Jump to bottom

TailwindCSS v4 #468

Open
2 of 3 tasks
qwerzl opened this issue Jan 27, 2025 · 1 comment · May be fixed by #506
Open
2 of 3 tasks

TailwindCSS v4 #468

qwerzl opened this issue Jan 27, 2025 · 1 comment · May be fixed by #506
Assignees
@qwerzl

Comments

@qwerzl
Copy link
Member

qwerzl commented Jan 27, 2025 •
edited
Loading

Now that TailwindCSS v4 is going stable, we should better support it.

  • Playground: Add TailwindCSS v4 example. It'd be ideal if we can find a way to keep v3 and v4 in one npm project.
  • Test: Test for TailwindCSS v4
  • Auto enable experimental.processCSSVariables if Tailwind v4 is detected (i.e. @tailwindcss/vite is installed)
@qwerzl qwerzl self-assigned this Jan 27, 2025
@qwerzl qwerzl mentioned this issue Jan 27, 2025
Merged
8 tasks
@MickL
Copy link

MickL commented Jan 29, 2025 •
edited
Loading

I think the last one is kinda crucial for a frictionless dx. Also there is a critical bug that makes the module unusable atm: #443

This was referenced Feb 18, 2025
Draft
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qwerzl qwerzl

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: auto enable experimental.processCSSVariables for tailwindcss v4 qwerzl/fonts
2 participants
@MickL @qwerzl