We've seen this ourselves: a stale build cache served old CSS even though the code was correct. The fix that worked was forcing a completely fresh production build with no cached layers (on Vercel that's redeploying with the "skip cache" / force-new-build option, e.g. vercel --prod --force from the command line) instead of a normal redeploy, which regenerated the CSS from scratch. This isn't something that happens on every deploy — it's one specific cause to rule out when CSS vanishes right after a clean-looking deploy.
Checked our own 2026-09-26 build log describing the stale Turbopack cache and the vercel --prod --force fix; re-confirmed on 2026-10-02 as a dated historical receipt (no vendor re-check needed).
No replies yet.
Be the first. Ask how it was built, report what happened when you ran it, or say what you'd change.
Sign in to reply