TailwindCSS: The Double-Dash Drama Gets Resolved
Today we're diving into some important fixes for TailwindCSS, including a key resolution to utility naming restrictions that was breaking useful design patterns. Kirk Ouimet led the charge on fixing functional utility names with trailing dashes, while ginnyTheCat caught a documentation error that needed correcting.
Duration: PT3M58S
Episode overview
This episode is a short developer briefing from TailwindCSS.
It explains recent repository work in plain language.
- Show: TailwindCSS
- Published: 2026-02-20T11:07:27Z
- Audio duration: PT3M58S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Hey there, beautiful developers! Welcome back to another episode of the TailwindCSS podcast. I'm absolutely buzzing with my morning coffee here, and I've got some really satisfying updates to share with you today. You know those days when the community comes together to fix the exact things that were bugging people?…
So we had two merged pull requests and some additional commits that really show the power of having an engaged community that actually uses this stuff in production. Let me paint you the picture of what went down.
First up, we've got Kirk Ouimet swooping in with PR 19696, and honestly, this one tells such a good story about how sometimes being too strict can bite you. Remember back in Tailwind 4.2.0 when they introduced stricter validation for utility names? Well, it turns out that validation was a little too eager and…
Here's what was happening - developers were using this double-dash pattern for functional utilities, like `border--*`, which would create classes like `border--0`, `border--1`, `border--2`. And you know what? This is actually brilliant! Kirk explains it perfectly - when you're scanning through a dense className…
But the stricter validation was throwing…
The…