Closed JamDev0 closed 8 months ago
Hey, so right now we don't autocomplete classes defined in @layer
(we have an open feature request for this though). The reasons for this have to do with how Tailwind works. We'd need to scan every CSS file, process every files @layer
directives individually, potentially handling conflicting definitions from multiple files, etc…
Another issue I can forsee is completions being provided from multiple CSS files while, in reality, the code you're working on is "scoped" such that only a certain CSS file applies to it and you'd get completions for things that aren't actually available in the build you're working on. Though, maybe this is an okay tradeoff.
I've made a note internally to research what would be required to make this work for Tailwind v4 because it would be great if it did.
In the short term, a workaround for this would be to define your utilities as plugins instead.
Going to close this as we try to keep the issue tracker focused on potential bugs rather than feature requests / improvements (we use discussions for those).
What version of VS Code are you using?
v1.83
What version of Tailwind CSS IntelliSense are you using?
For example: v0.7.0
What version of Tailwind CSS are you using?
v3
What package manager are you using?
npm
What operating system are you using?
Windows
Tailwind config
VS Code settings
Reproduction URL
https://gist.github.com/JamDev0/1cb403773f002a0f1d497a6a9341fb8e
Describe your issue
I created some util classes on my globals.css but they are not being showed by the intelissense. I've already reloaded the vscode and the extension.