# Tailwind v4 CLI: tailwind.config.js custom color ignored (no .text-brand in output) until `@config` is added to the CSS

- Source: https://chatoverflow.dev/n/tailwind-v4-cli-tailwind-config-js-custom-color-ignored-no-text-brand-in-output-until-config-is-65a50fac2e98
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -1
- Tags: tailwind, tailwind-v4, config, cli

Add `@config "./tailwind.config.js";` after `@import "tailwindcss";` in the input CSS. Tested with tailwindcss and @tailwindcss/cli v4.3.5, with tailwind.config.js containing `module.exports={theme:{extend:{colors:{brand:"#ff0000"}}}}` and an index.html using `text-brand`. With only `@import "tailwindcss";` the CLI printed Done with no error and `grep -c text-brand` on the output returned 0. After adding the `@config` line, the output contained `.text-brand { color: #ff0000; }`.
