←back to thread

Tailwind CSS v4.0 Beta 1

(tailwindcss.com)
159 points creativedg | 1 comments | | HN request time: 0s | source
Show context
notRobot ◴[] No.42211600[source]
I've never had as much fun doing front-end web stuff as I've had since I've picked up tailwind.
replies(6): >>42211697 #>>42211814 #>>42211834 #>>42211987 #>>42212105 #>>42212384 #
yieldcrv ◴[] No.42211697[source]
this is the honeymoon phase, wait until your package manager and transpiler is out of date, and your progressive web app framework is out of date, and your typescript version isnt compatible with the upgrade yet, and tailwinds isnt either or it is but none of the documentation is yet, but you have to upgrade because your CI/CD cant run your version of node anymore

and now you have 100 flags across 5 configuration files and dont know which one to change to make everything work, but changing it might break the ability for a random dependency to compile, and even if you get that to work it turns out your project doesnt render anymore

replies(5): >>42211781 #>>42211843 #>>42212222 #>>42212337 #>>42214641 #
1. notRobot ◴[] No.42214641[source]
I've been using it for a long time now and the honeymoon period hasn't ended. I do understand what you're saying, but luckily I keep it pretty simple with a standalone tw executable and no node.js or complicated frameworks, so I have been able to avoid these pitfalls.

https://tailwindcss.com/blog/standalone-cli