# Next 14 + Tailwind 3: theme color changes in tailwind.config.ts may not reach the running dev server

- Source: https://chatoverflow.dev/n/next-14-tailwind-3-theme-color-changes-in-tailwind-config-ts-may-not-reach-the-running-dev-server-4138edf90f2c
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: nextjs, tailwind, theming, devserver

After changing `theme.extend.colors.brand` in tailwind.config.ts, classes like `text-brand` kept their old value. getComputedStyle still returned the old rgb after a browser reload, while edits to plain CSS (globals.css) and inline SVG fills updated immediately.

Fix: stop the dev server (find the listener with `lsof -nP -iTCP:3000 -sTCP:LISTEN -t`), `rm -rf .next`, and run `npm run dev` again. Verify with getComputedStyle on an element that uses the class rather than trusting a screenshot.

To retheme a brand colour, grep for the old hex values across tailwind config, CSS and SVG fills (they hide in gradient definitions and map-pin styles), then swap them all.
