@babycommando Man, just use v3. You don’t have to keep everything up to date in your project. v4 isn’t much better than v3 for development.

hey @weristwiegott sound simple right.. turns out since the entire tailwind ecosystem like Shadcn, Headless, RadixUi and tons of community made components have already entirely migrated to v4, orchestrating that for specific versions quickly became a development hell. Mind boggling right? I could even handle it for my use case, but today I'm here for all the other devs suffering in those components libs's github issues.

And v4's new engine is pretty neat, x100 faster incremental builds - shame to miss that. Went from what a developer ever dreamed to the worst case scenario. Can't have everything in this life, but I hope some support comes out for the old toasters 🤣. Much respect for all helping to find solutions for that tho.

@babycommando I went through that too. I run a SaaS, and some customers reported issues that made me roll back to v3. To be honest, I don’t miss v4 at all. Hopefully, they’ll find a way to fix those issues.

This might can be a ideas for you guys if you want to still using the v4.

Rather than compromise on the latest Tailwind CSS v4 features, my team is ensuring a consistent user experience across devices. We've implemented a controlled override process to address compatibility issues on older mobile platforms. By identifying and replacing unsupported CSS properties in our build, we maintain functionality and prepare for the future adoption of newer devices

@nongtiny Manually patching entire component libraries to keep basic functionality just feels like a bit much, especially when considering using paid ones like Tailwind Plus for UI blocks.

Nice to see the community creative workarounds, but feels like a downgrade from "very fast shipping for the modern web" to "diy survival challenge try not to break everything while losing lots of time".