(tailwindcss.com)

159 points creativedg | 2 comments | 22 Nov 24 02:12 UTC | HN request time: 0.001s | 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?

1. lenkite ◴[22 Nov 24 08:39 UTC] No.42212149[source]▶

Generally use the standalone tailwind CSS CLI tool for keeping things lean. Sadly the download link from the "Getting Started" page https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.... is broken.

Shows that the "bloated" way of doing things is now the norm.

replies(1): >>42213281 #

2. 0x6c6f6c ◴[22 Nov 24 12:28 UTC] No.42213281[source]▶

This is a feature for projects already using Node and Vite (which is quite popular these days).

It's also not a requirement. The binary still exists, you can run it standalone.

Tailwind CSS v4.0 Beta 1