frontend6 min read
Tailwind v4 Classes Not Working? Six Causes, Each Tested
Custom colors, bg-* or p-4 doing nothing after upgrading to Tailwind v4? Six causes, each reproduced against the real compiler, with the one-line fix for each.
·Adesh Shukla
Tag
3 posts
Custom colors, bg-* or p-4 doing nothing after upgrading to Tailwind v4? Six causes, each reproduced against the real compiler, with the one-line fix for each.
DevStash runs Tailwind v4 with every token in @theme, not tailwind.config.ts. What that migration actually breaks, and one silent-failure gotcha worth knowing.
How I architected a developer platform on Next.js 16, Tailwind v4 and a file-based content layer — the decisions that held up, and the ones that cost me hours.