←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: 0.206s | source
Show context
kookamamie ◴[22 Nov 24 08:33 UTC] No.42212127[source]▶
Read some of the Getting Started documentation, for fun. First step:

> Installing with Vite

What the hell is Vite? Oh, it seems to be something you need to install via npm.

I cannot help but to ask - why do we require npm, or Vite, for something that looks like it should "help" with CSS?

Why is the webdev such a shitshow, that seems to get ever deeper into its own weird rabbit hole?

replies(13): >>42212149 #>>42212151 #>>42212155 #>>42212163 #>>42212304 #>>42212348 #>>42212380 #>>42212593 #>>42212640 #>>42212864 #>>42213311 #>>42214964 #>>42217238 #
1. Leonelf ◴[22 Nov 24 10:30 UTC] No.42212640[source]▶
Are you just lazy? Apart from not being up to date with common ecosystems (which I'd expect when doing anything web), look at the Getting Started:

Getting started ->Installing with Vite ->Installing with PostCSS ->Installing the CLI ->Upgrading from v3

At the bottom of the CLI paragraph it says "You can also download standalone builds of the new CLI tool from GitHub for projects that don’t otherwise depend on the Node.js ecosystem."

They just put the most common stuff at the top, because that's what most devs will use.