Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`class` types appear to have React bleed-in

See original GitHub issue

I suspect this might not be really a Volar issue but i’m not sure where else to turn at the moment. I have a documentation site that is based off of @antfu’s popular Vitesse plugin and all of my .vue files are reporting errors on the class property:

with the language around className i’m suspecting that something that likes React is interfering as I have another repo on the same machine which is behaving correctly. That said, if you look at the direct dependencies of this project they are all pretty much “the usual suspects”:

"dependencies": {
    "@vueuse/core": "^7.5.5",
    "@vueuse/head": "^0.7.5",
    "date-fns": "^2.28.0",
    "floating-vue": "^2.0.0-beta.5",
    "inferred-types": "^0.18.4",
    "nprogress": "^0.2.0",
    "pinia": "^2.0.11",
    "prism-theme-vars": "^0.2.2",
    "tauri-search": "workspace:*",
    "vue": "^3.2.29",
    "vue-demi": "^0.12.1",
    "vue-i18n": "^9.1.9",
    "vue-router": "^4.0.12"
  },

with my own repo being the sole outlier but it’s dependencies are relatively innocuous too:

  "dependencies": {
    "axios": "^0.25.0",
    "dotenv": "^14.3.2",
    "fast-glob": "^3.2.11",
    "inferred-types": "^0.18.4",
    "native-dash": "^1.21.5"
  },

the last two are my own repos but I’m using these with Volar in other repos without issue. Is there any way that a dev-dep could interfere? Is there anyway to work around this? The impact is quite large in that my Vue templates no longer format/indent anymore (plus all those red squigglies are slowly driving me mad).