Fix errors thrown by detecting content files with oxide (#942)

tailwindlabs / tailwindcss-intellisense

Intelligent Tailwind CSS tooling for Visual Studio Code

2.74k stars 183 forks source link

Fix errors thrown by detecting content files with oxide (#942) #945

Closed hampustagerud closed 3 months ago

hampustagerud commented 3 months ago

I had the same problem as described in #942, which seem to have been closed preemptively 🙂 By adding oxide as a devDependency and then checking the import with a type guard we get an error that explains the issue:

So by ignoring the globs when creating the DocumentSelectors, normalizePath no longer throws and the server starts up properly in a fresh v4 setup 👍

thecrypticace commented 3 months ago

Ah right the types (and returned data) changed here at some point during development. I'll get this fixed up and merged in today.

thecrypticace commented 3 months ago

Thanks!