[v4] Vite duplicating index.css on hot reload after Tailwind CSS update

[alex-x-x-x-x]

After upgrading Tailwind CSS to version 4, my Vite project is unexpectedly logging multiple instances of /src/index.css on startup, for context I'm on v4.0.4 (Tailwind) and v.6.10 for Vite. I'd also like to remark that this behavior was not present before the update.

Has anyone else encountered this? Could this be a known issue with Tailwind 4, or is it potentially related to how Vite processes CSS files on this new update? 🧐

Steps to Reproduce

1. Upgrade Tailwind CSS and Vite to the latest versions:

npm install -D tailwindcss@latest vite@latest

2. Start the development server:

npm run dev

3. Observe that multiple instances of /src/index.css appear in the terminal logs upon startup.

Troubleshooting Attempts

I have attempted the following steps to identify the cause of the issue:

• Checked main.jsx → index.css is only imported once, ensuring there are no duplicate imports in the entry file.
• Searched the project for unexpected imports using:
  grep -r "index.css" src/ — no other files appear to be importing it.
• Cleared Vite’s cache and restarted the dev server:
  rm -rf node_modules/.vite && npm run dev

I also modified the content paths in tailwind.config.js, but this did not resolve the issue.

[philipp-spiess]

@alex-x-x-x-x Hey! Are you using @taiwlindcss/postcss or @tailwindcss/vite? Only upgrading the tailwindcss will not be enough since it's no longer a postcss plugin by default: https://tailwindcss.com/docs/upgrade-guide#using-postcss

[alex-x-x-x-x]

@philipp-spiess Hey Philipp! I'm using @tailwindcss/vite

[dvrtnkv]

node_modules/@tailwindcss/node/dist/index.mjs

function I(s){if(s.includes("/.vite/"))return;let n=(V(s)==="css"||s.includes("&lang.css")||s.match(K))&&!z.test(s)&&!J.test(s);return n&&console.log(n),n}

temporarly fix for me is just remove console.log and extra n:

function I(s){if(s.includes("/.vite/"))return;let n=(V(s)==="css"||s.includes("&lang.css")||s.match(K))&&!z.test(s)&&!J.test(s);return n}

[wongjn]

This should now be fixed in v4.0.5.

[alex-x-x-x-x]

Thanks a ton! @wongjn 🎉