News for hackers. Stuff that matters.
Re:Tailwind CSS v4.0 Beta 1 by kookamamie on Friday November 22, 2024 @03:48AM (#42212179)
CSS is text. What's wrong with copying the required CSS stylesheets over and including (importing) them from your own stylesheets?

Surely we don't need a "package manager" and a "build chain" for this?

Then again, I'm a person that writes any web-related code (HTML, JS, CSS, etc.) by hand.

Where did we take the left-turn of not understanding how things work on the actual tech level? These tools hide all of the actually required steps to npm-infested bloat.

Re:Tailwind CSS v4.0 Beta 1 by ahussain on Friday November 22, 2024 @04:06AM (#42212263)
The number of tailwind classes is so large now that copy/pasting the whole set into your project would mean a huge bundle size.

Part of that the tailwind package is doing is making sure that only the relevant tailwind classes are included.

Re:Tailwind CSS v4.0 Beta 1 by dotancohen on Friday November 22, 2024 @04:37AM (#42212429)
So Vite builds a custom style sheet based upon the Tailwind classes that are actually used in the project?
Re:Tailwind CSS v4.0 Beta 1 by agos on Friday November 22, 2024 @04:59AM (#42212521)
yes, exactly
Re:Tailwind CSS v4.0 Beta 1 by macguillicuddy on Friday November 22, 2024 @03:57AM (#42212219)
x86 ASM is text but we don't build software by copying and pasting it. While the underlying thing we ship is CSS, that doesn't mean we can't add tooling layers to make it easier or more efficient. While it's totally allowed to write by hand, most frontend web developers I know are very comfortable with NPM, and indeed having dependencies consumed from a package manager is often preferred.