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.
10 articles
Start here
Tailwind v4 Compiles at Build Time, My New Classes (pl-16, h-7) Did Nothing in Production
-
Footer `lg:grid-cols-[1.6fr_repeat(6,minmax(0,1fr))]` Collapses to Three Columns in Tailwind v4? Arbitrary Values That Vanish at Compile
August 31, 2026 -
Clipped Letters in Big Headings? Tailwind v4 `text-5xl` Quietly Ships `line-height: 1`
August 8, 2026 -
Hero Text Overlapping the Phone Image on Mobile? `object-cover` Silently Re-centers When an `absolute` Layer Stretches Past `min-height`
July 30, 2026 -
`next/font` Not Applying in Tailwind v4? `var()` Inside `@theme` Resolves at Build Time, Not Runtime
July 14, 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 10, 2026 -
Utility Classes Lose to `.prose-dark h4` by Specificity, Wrap Prose Rules in `:where()`
July 3, 2026 -
Tailwind v4 `@source` Resurrects Classes You Already Deleted, Exclude the Seed/Import Folder
July 3, 2026 -
Tailwind v4 Preflight Kills WordPress `alignleft`/`alignright`, Restore It Without `clear:both` on Headings
July 2, 2026 -
Tailwind v4 Tree-Shook My CSS Variable → Text Shipped Invisible White in Production
June 21, 2026