-
-
Notifications
You must be signed in to change notification settings - Fork 353
Description
The current project is using tailwindcss v3.2.4. Tailwind CSS v4 is a significant update offering a new high-performance engine and simplified configuration.
Reasoning
Performance: v4 is significantly faster (builds are up to 10x faster).
Modernization: Aligns with the latest web standards and simplifies the tech stack.
Developer Experience: CSS-first configuration reduces context switching between JS and CSS files.
Potential Risks
Breaking Changes: v4 changes how tailwind.config.js works (it's often not needed) and how @tailwind directives are used.
Migration Effort: We will need to audit our custom theme extensions (colors, fonts) to ensure they migrate correctly to CSS variables.
Proposal I propose we upgrade to Tailwind CSS v4.
Audit: Identify all custom config in tailwind.config.js.
Upgrade: Update dependencies (tailwindcss, postcss, etc.).
Refactor: Migrate configuration to CSS variables or the new v4 format.
Verify: Check all pages for visual regressions.
Is the team ready for the upgrade??