(untitled)

Lightning CSS is not fit for purpose.

(╯°□°)╯︵ ┻━┻

It’s practically impossible to control what CSS is actually output. The documentation and config are infuriating on missing details.

It’s not a problem until it’s a problem. As soon as you try to fix issues like animation shorthand a side effect is triggered elsewhere.

Lightning CSS is like one of those mini-games where you have to activate a row of switches but when you toggle one switch others are inverted. That game sucks.

I’m back to using ESBuild to bundle and minify CSS. If minification doesn’t matter, and it rarely does with HTTP compression, I’m using ten lines of janky Node.js to bundle CSS imports myself.

ESBuild is annoying too. I had to write a custom plugin shim to flag font and image URLs and “external” otherwise it cried about path resolution. I just want to bundle imports! Why is there no option to do the most basic thing?

I’m convinced none of these tool developers ever build real websites. Modern dev tools all have main character syndrome. Sorry, you’re not that important. By all means have your cryptic JSON dot file and CLIs for the converted. But please just export the no-nonsense primitive parts as a code library.