Build plugin/config relocation
Tailwind CSS v4 JavaScript config file not auto detected @config content sources theme tokens vanish upgrade
Custom theme tokens and content sources vanish after upgrade.
Agent Quick Fix
Repair against the current Tailwind CSS contract, then keep the change narrow and source-backed.
Product: Tailwind CSS
Current-contract area: Tailwind v4 JavaScript config is no longer auto-detected
Likely root cause: Custom theme tokens and content sources vanish after upgrade.
Repair direction: Verifier checks the current package identity/config format and a real transformed output. Verify a minimal current configuration and actual generated CSS.Symptom
Custom theme tokens and content sources vanish after upgrade.
Why This Happens
The old package/config name is syntactically valid, but current tool packaging and discovery rules live in external release documentation.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Tailwind CSS v4 JavaScript config file not auto detected @config content sources theme tokens vanish upgrade
site:tailwindcss.com/docs/functions-and-directives @config Tailwind CSS v4 config file
https://tailwindcss.com/docs/upgrade-guide
'@config' in https://tailwindcss.com/docs/functions-and-directives
'Using a JavaScript config file'