TailwindCSS: Vite CSS Resolver Fix
A single fix in the Vite plugin ensures custom resolve conditions set in a project's Vite config are no longer silently dropped during CSS import resolution, bringing behavior in line with how JavaScript imports already work.
Duration: PT2M10S
Episode overview
This episode is a short developer briefing from TailwindCSS.
It explains recent repository work in plain language.
- Show: TailwindCSS
- Published: 2026-08-22T13:04:52Z
- Audio duration: PT2M10S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 22nd, and here's your TailwindCSS briefing.
Today's activity is small but worth knowing if you're using Tailwind's Vite plugin with custom export conditions. PR 20428, from contributor loulanyue, fixes a quiet inconsistency between how CSS and JavaScript imports were resolved.
Here's the issue: when Vite resolves a JavaScript import, the JS resolver respects any custom conditions you've set in your resolve conditions configuration. But the CSS resolver was doing something different — it was overwriting those settings entirely with a hardcoded list of style and development-or-production…
The fix, tied to issue 20426, appends the user's configured conditions onto the default CSS list instead of replacing them. That's a meaningful reliability fix for anyone publishing or consuming packages with custom export conditions — think design systems or component libraries that ship different CSS entry points…
The theme here is consistency between resolvers. When two code paths that should behave the same way quietly diverge, bugs like this can sit unnoticed for a while — since everything still builds, it just builds with the wrong assumptions.
What's next: if you rely…