Hey @Sebb , I think that’s a bug in the vscode extension. This github issue is a bit of a grab-bag but some of the comments down thread make it clear others are having issues getting tailwindcss-intellisense to find the standalone tailwindcss executable.
I’m keeping a watch on that issue. In the meantime I’ve npm installed tailwind in my assets folder, just for the extension’s use, and excluded all the resulting node cruft in .gitignore. Ugly, but I find it just about worthwhile as a workaround.
