Topic
Tailwind v4 Build-Time Pitfalls
Tailwind v4 decides a lot at build time, not runtime, and that's where your classes silently disappear. Tree-shaking that drops a CSS variable, `@source` resurrecting classes you already deleted, and `var()` inside `@theme` that never resolves. Read this when a utility class 'does nothing' in production but works fine in dev.
7 articles
Start here
Tailwind v4 Compiles at Build Time, My New Classes (pl-16, h-7) Did Nothing in Production
`next/font` Not Applying in Tailwind v4? `var()` Inside `@theme` Resolves at Build Time, Not Runtime
July 9, 2026
Text With `text-[oklch(0.97_0.01_260/0.80)]` Renders With No Color in Tailwind v4? The Trailing Zero Means the Class Never Compiles
July 4, 2026
Tailwind v4 `@source` Resurrects Classes You Already Deleted, Exclude the Seed/Import Folder
June 27, 2026
Utility Classes Lose to `.prose-dark h4` by Specificity, Wrap Prose Rules in `:where()`
June 27, 2026
Tailwind v4 Preflight Kills WordPress `alignleft`/`alignright`, Restore It Without `clear:both` on Headings
June 26, 2026
Tailwind v4 Tree-Shook My CSS Variable → Text Shipped Invisible White in Production
June 12, 2026