chore: Tailwind CSS v3 → v4 migration #99
Reference in New Issue
Block a user
Delete Branch "feat/tailwind-v4-upgrade"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
@tailwindcss/upgradetool — upgraded to v4.2.1, deletedtailwind.config.js, migrated@theme+ class names across 128 files@tailwindcss/postcssto@tailwindcss/viteplugin, deletedpostcss.config.js@theme, eliminatedhsl(var(--))double-indirection across 17 component files, fixed@custom-variant darksyntaxKey changes
@themeblock (no moretailwind.config.js)@tailwindcss/vitefor faster HMR (no PostCSS intermediary)@theme(v4 pattern)autoprefixer(built into v4)Test plan
npm run buildpasses cleanlytsc --noEmitpasseshsl(var(--patterns in codebase🤖 Generated with Claude Code
🚅 Deployed to the patherly-pr-99 environment in selfless-grace