TailwindCSS: PostCSS Cache Fix Closes Stale Build Gap

A single merged fix ensures the PostCSS plugin rebuilds when input CSS changes even if the source file's modification time doesn't, closing a caching gap for tools like Sass that pipe CSS through without touching the file on disk.

Duration: PT2M2S

Episode overview

This episode is a short developer briefing from TailwindCSS.

It explains recent repository work in plain language.

  • Show: TailwindCSS
  • Published: 2026-07-06T13:03:57Z
  • Audio duration: PT2M2S

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 July 6th, and today's briefing covers one focused but important fix in the Tailwind ecosystem.

The headline: the PostCSS plugin had a blind spot in how it decides whether to do a fast, incremental rebuild or a full one. It relied on comparing modification times across the entry file and its imported config and plugin graph, but it never actually checked whether the input CSS itself had changed. That's a…

PR 20310, from contributor Lazerg, fixes this by storing the input CSS alongside each cache entry. Now, if the incoming CSS differs from what was cached, the plugin falls back to a full rebuild, the same safety net the CLI watcher already had for changed input files. This closes a gap between two tools that were…

Worth noting for anyone relying on build tooling: this was a silent failure mode. No error, no warning, just outdated CSS shipping to production. The fix was verified with a regression test that reproduces the exact scenario, two different CSS inputs mapped to the same on-disk file, confirming the bug on the main…

What's next: if your pipeline feeds generated CSS into Tailwind's PostCSS plugin without writing intermediate files, this update is worth…

That's…

Nearby episodes from TailwindCSS

  1. Weekly Recap - Correctness Fixes and CLI Watch Mode Returns
  2. Attribute Selector Parsing Fixed
  3. Quiet Edge Cases in Variants and Modifiers
  4. Weekly Recap - Source Handling & Developer Experience
  5. Minor Documentation Cleanup
  6. Type Safety and Grid Utilities Update
  7. Developer Experience Improvements
  8. Source Directive Scanning Improvements