TailwindCSS: Source Directive Scanning Improvements
Three fixes landed focusing on the @source directive's file scanning behavior, resolving issues with git-ignored folders and over-scanning from complex glob patterns. The changes improve build performance by ensuring more precise file discovery.
Duration: PT2M5S
Episode overview
This episode is a short developer briefing from TailwindCSS.
It explains recent repository work in plain language.
- Show: TailwindCSS
- Published: 2026-06-11T13:05:58Z
- Audio duration: PT2M5S
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 June 11th, 2026. I'm your host with today's TailwindCSS developer briefing.
The main story today is a focused effort to fix how TailwindCSS handles @source directives, with two significant scanning improvements that directly impact build performance and reliability.
The core issue centered around @source directives not behaving as developers expected. Pull request 20214 resolved a problem where explicitly adding git-ignored folders through @source would still be ignored by the scanner. The fix involved promoting these sources from "Auto" to "External" classification internally,…
The second major fix in PR 20217 addressed over-scanning caused by complex glob patterns. When you specified something like "blog/*/foo/bar/baz/**/*", the scanner was losing the dynamic path information and scanning too broadly. Now the system preserves these pattern segments as proper pattern sources rather than…
Both changes modify the internal source entry classification system, moving between Auto, Pattern, External, and Ignored categories based on the specific use case. This ensures the scanner respects developer intent while maintaining performance.
The practical impact is faster…