Tailwind CSS v4.2.4: Vite Alias Resolution Fix for @import and @plugin

Tailwind CSS has released v4.2.4, a patch version that addresses a key bug in the @tailwindcss/vite plugin. The update ensures that Vite aliases configured in your build pipeline are properly resolved when used in @import and @plugin directives.

Changes in This Release

• Fixed alias resolution for @import and @plugin when using Vite aliases in @tailwindcss/vite (pull request #19947).
• The fix applies specifically to the @tailwindcss/vite plugin, ensuring that paths like @/styles/tailwind.css defined via Vite's resolve.alias are correctly resolved.
• No breaking changes or new features are included; this is a pure bug-fix release.

Why This Matters

For developers using Vite aliases to simplify import paths (e.g., importing Tailwind configuration or custom CSS files from a central location like @/app/styles), this bug could cause builds to fail or generate incorrect CSS. With v4.2.4, workflows that rely on aliases for modular project structures now work seamlessly. This fix is especially relevant for large projects that organize CSS files across directories, as well as those integrating third-party @plugin packages with alias-based paths. The update is backward-compatible and requires no configuration changes—simply upgrading to v4.2.4 restores expected behavior.

Source: https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.2.4