Daffa Pramuditya Daffa P. Roles: Web Developer, Freelancer, AI Engineer [ Web DeveloperFreelancerAI Engineer Web Developer ]
[ 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.
← All articles 11 articles
Browse by topic
- WORDPRESS-PHP WordPress & PHP in Production 69
- ELEMENTOR Elementor: Under the Page Builder's Hood 25
- CACHING-CDN Caching & CDN: Deployed, but Nothing Changed 19
- SEO-REDIRECTS Technical SEO, Redirects & Migrations 18
- CSS-LAYOUT CSS Layout, Overflow & Cascade 36
- TAILWIND Tailwind v4 Build-Time Pitfalls 11
- NEXTJS-REACT Next.js & React in Production 47
- SHOPIFY-LIQUID Shopify, Liquid & the Theme CLI 13
- JAVASCRIPT-DOM JavaScript, DOM & Browser Animation 60
-
Jun 22, 2026
-
Sep 29, 2026
-
Aug 31, 2026
-
Aug 8, 2026
-
Jul 30, 2026
-
Jul 14, 2026
-
Jul 10, 2026
-
Jul 3, 2026
-
Jul 3, 2026
-
Jul 2, 2026
-
Jun 21, 2026