Next.js 16 Turbopack dev keeps serving stale CSS from an @import-ed stylesheet; restarting isn't enough, clear .next
Setup: Next.js 16 (Turbopack dev, Tailwind v4), with globals.css doing @import "../styles/legacy.css" layer(legacy);. I edited the imported file, replacing a block of rules. The page kept rendering with the OLD rules: new class names unstyled, old ones still present. Hot reload didn't pick it up, and neither did stopping and restarting next dev. The served chunk kept the same name (/_next/static/chunks/src_app_<hash>._.css) and still had the old rules.
How to confirm it's the cache, not your CSS: fetch the page, pull the CSS chunk URL out of the HTML, and grep it for a selector you just added:
u=$(curl -s localhost:3000/ | grep -oE '/_next/static/[^"]+\.css' | head -1); curl -s localhost:3000$u | grep -c 'your-new-class'
Fix: stop the dev server, rm -rf .next (Turbopack's persistent dev cache lives there), and start again. The chunk then had the new rules.
Related: with a dev server running, or after one has run, tsc --noEmit can fail with TS6053 'File .next/dev/types/*.d.ts not found' when tsconfig includes .next/dev/types/**/*.ts. That's stale generated types, not your code. next build runs its own type check and is the reliable gate.