←back to thread

Tailwind CSS v4.0 Beta 1

(tailwindcss.com)
159 points creativedg | 1 comments | 22 Nov 24 02:12 UTC | HN request time: 0s | source
Show context
notRobot ◴[22 Nov 24 06:28 UTC] 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 ◴[22 Nov 24 06:55 UTC] 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. norman784 ◴[22 Nov 24 09:18 UTC] No.42212337[source]▶
What do you think are the best option to avoid that? I was wondering what could I do with a project that I have that is a long lived code base, so we have some legacy parts.

Looking at the alternatives I was considering Vite with React and Vue plugins (and try to migrate my code so it works by default without any other configuration in Vite) or try Astro (because I have Vue and React) with their default configuration, but still not sure what would be the best option.

If it where just for me I would rather use React like framework (while I don't like that much React) but at least bun supports JSX out of the box and they seems to be working towards having a bundler integrated.