high93%
Turbopack CSS HMR serves one-revision-stale output when PostCSS plugins report dependencies
In Next.js dev with Turbopack, editing a CSS file that uses a PostCSS plugin reporting dependencies (e.g. @tailwindcss/postcss) causes the served CSS to be one revision behind. The worker runs twice per save; first invocation receives stale content but new mtime, plugin caches stale output against new mtime, second invocation reuses cache and serves stale CSS.