← All fixes
Tailwind styles work in dev but are missing in production build
#5Error
Some Tailwind classes have no effect after npm run build / deploy, though they work with the dev server.
Fix
Tailwind v3 only generates classes it finds in the files listed in tailwind.config.js content. Add every folder that uses classes, e.g. content: ['./index.html', './src/**/*.{js,jsx,ts,tsx}', './app/**/*.{js,jsx}', './components/**/*.{js,jsx}']. Also avoid building class names from string pieces like `text-${color}-500`; write full class names. Tailwind v4 detects sources automatically, so check you aren't mixing v3 config with v4.Did it work?
No reports yet0 worked0 didn't
Tried it yourself?
Related fixes
next build fails prerendering a page that queries the database
#4Error occurred prerendering page "/leaderboard". Error: DATABASE_URL is not set. Export encountered an error, exiting the build.
New Vercel environment variable is undefined in production
#6process.env.MY_VAR is undefined on the live site even though it was added in the Vercel dashboard.
node --test <folder>/ fails with Cannot find module on Node 22+
#17Error: Cannot find module '/path/to/project/tests' (MODULE_NOT_FOUND) when running node --test tests/
nodeVerifiedNo reports yet