Make an element that is hidden that has all possible values of classes you can use. Or use normal css for that one part of your app if that isn’t possible. Lots of ways you can handle this without thinking the framework doesn’t work.

Ninja:

https://tailwindcss.com/docs/content-configuration#safelisting-classes

Tailwind actually has this use case covered already. Use the safe list functionality to always include the classes you need.

Unless you are going to be allowing custom html to be added the tooling is smart enough to figure out what possible classes your code can use. You’d have to do something dumb to not have the tools able to tell what components you are serving.

Ok so use modern frameworks and tools that implement the tailwind plugin. Because if you are shipping the entire tailwind css that’s a developer problem not tailwinds. News flash: using a technology wrong doesn’t make the tech wrong.

Language Server Protocol. It’s how programs (language servers) can talk to your editor (like vs code or nvim) and provide refractors and intellisense and what not.