Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

kokoshneta's avatar

Getting Tailwind to work *properly* in VSCode

I’ve been searching for a while now for ways to get Tailwind to work properly in VSCode, but I can’t find anything. This is what I have found (and also applied):

  • how to turn off built-in linting and use Stylelint instead
  • how to suppress “unknown at-rule” warnings
  • how to add Tailwind IntelliSense so you get auto-complete in Blade and CSS files
  • how to add custom at-rule data for plain CSS to get auto-completion for @ directives

But all this still leaves the biggest issue of all for me, namely that anything inside an unknown at-rule is ignored completely. No linting, no IntelliSense, no auto-complete – and most crucially, the Go to symbol in editor command (Cmd + Shift + O) won't find anything inside an unknown at-rule.

So all my custom CSS, which I’ve painstakingly put inside the appropriate @layer rule, is un-goto-able. I can quickly jump to any rule I’ve defined outside the Tailwind layers, but as soon as I put it inside a layer, nada.

Is there really no way to get VSCode to recognise rules inside @layer directives in SCSS files?

0 likes
1 reply
kokoshneta's avatar

*bump*

No one knows of a way to get VSCode to deal properly with Tailwind?

Please or to participate in this conversation.