In the Vite environment, some categories cannot be hot reloaded and the service must be restarted.

[sdf09]

What version of Tailwind CSS are you using?

For example: v4.1.14

What build tool (or framework if it abstracts the build tool) are you using?

vite:7.1.9,
tailwindcss:4.1.14,
@tailwindcss/vite:4.1.14

What version of Node.js are you using?

Version: v20.12.0

What browser are you using?

Browser: Chrome

What operating system are you using?

Operating system：Windows

Reproduction URL

Describe your issue

When I use Tailwind CSS in Vite, I find that some classes don't work properly, such as w-2/10, z-4, or h-2/5. I have to restart my service before these classes take effect.

When I'm using it, I must restart the service

[wongjn]

Consider providing a git repo that reproduces the issue and we can take a look for you.

[sdf09]

考虑提供一个重现问题的 git 存储库，我们可以为您查看。

https://github.com/sdf09/Use-tailwindcss-exceptions-in-Vite.git
You can reproduce my problem through this repository. You can modify the login-content element in/ page/login/index.vue. You can try to change h-3/5 to h-3/7. You will find that it does not take effect immediately. At this time, you need to restart the service

[hood]

This could also not be Vite-specific and be a regression in one of the latest releases. I’ve noticed hot reloading stops working for some time (meaning it only restores it behaviour after a few minutes) for some TailwindCSS classes in one of my most up-to-date Next.js projects too.

I know this is not comparable to a proper repro, but for now reproducing my project would be kind hard, yet maybe this could be useful to the maintainers to figure something out:

❌ doesn’t work

opacity-50 group-hover:opacity-80

✔︎ works

opacity-50 group-hover:opacity-100

And with “doesn’t work”, I mean that nothing is getting generated, even after multiple saves, in my output CSS, even though the LSP is correctly picking up the value, so it’s not like I’m entering some invalid variant.

Screen.Recording.2025-10-28.at.10.45.19.mov