Post

Using CSS as a config in Tailwind 4 was a mistake.

This post is unavailable.

@jbhutch.bsky.social

I find the v4 config so much more difficult to use. Half the plugins don't seem to work anymore. UnoCSS is a bit more complex, but I find myself understanding better and I can always find a way to get it to work the way I like.

Luke Bennett

@lukebennett.dev

Creating a new DSL and jamming it into CSS seems like a really bad idea. Now I have to reference the docs constantly, and I’ve lost all the type safety. Plugins are also now considered “legacy” according to the docs ☹️

23/1/26, 4:31 am0 reposts0 likes

JB Hutch

@jbhutch.bsky.social

23 Jan

Yeah. Plugins, particularly the Typogroahy plugin, not working properly in v4 and this issue really confuse me github.com/tailwindlabs...

github.com[v4] `addComponents` is adding styles to `@layer utilities` instead of `@layer components` · Issue #15045 · tailwindlabs/tailwindcssWhat version of Tailwind CSS are you using? v4.0.0-alpha.34 What build tool (or framework if it abstracts the build tool) are you using? @tailwindcss/cli Reproduction URL https://github.com/saadegh...