[djmashko2]

Looks like a lot of great improvements, but wanted to put in one vote in favor of keeping the capability of having a JavaScript-forward configuration/usage approach, rather than requiring a CSS-forward approach.

For us, one big benefit of using Tailwind has been that we can avoid spending a lot of time thinking about CSS and CSS tooling, and being able to configure everything via JS has helped in that regard.

[jaredcwhite]

That's exactly why critics of Tailwind (like myself) have been so frustrated…Tailwind shouldn't mean you avoid spending time "thinking about CSS". CSS should be a principal and respected pillar of a website's architecture, every bit as vitally important to reason about and understand as anything JS-related. Tailwind v4 promoting CSS-first configuration and customization, and allowing design token usage in vanilla CSS, knocks down a major complaint we've had regarding the framework.