Issue with Pug template v2.0.0 - never read warning

[juzser]

Seem likes the new version has not been compatible with template using pug yet?
I'm using the components and methods on template but it's still showing unused warnings.

[JayPuff]

I thought I was going crazy from running into the same issue after having set up my typescript/linting within our pug templates last week and having no issue. Unfortunate timing I guess.

Yeah, seems like it's a language tools v2.0 issue on composition API components, whether lang="ts" is on or not

Previously the work around for fake positives on 'never read' values were fixed by adding "@vue/language-plugin-pug" to the vueCompilerOptions on tsconfig, but I don't think that would make it an issue relating to that package

[richardsimko]

Option clicking on references in the template also no longer works, could be related.

[JayPuff]

Option clicking on references in the template also no longer works, could be related.

Yeah likely the same issue, same for hovering over script variables in the template which would usually give type info

[fengjac]

Same issue

[JayPuff]

2.0.5 does not resolve the issue with the never read warning for me, even after re-installing the extension and rebooting vscode.

It also still does not validate ts within the template section, so it doesn't highlight things like calling a method with incorrect params, or have any type info on hover. while running vue-tsc will clearly show the ts errors within pug template.

Has anyone managed to get it to work for them?

I have this in my tsconfig.json as well since it was required before language tools v2.0:

"vueCompilerOptions": {
    "plugins": [
      "@vue/language-plugin-pug"
    ]
  }

environment details

Version: 1.87.0
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:16.599Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 5.11.0-37-generic snap

[fardolieri]

Have you made sure to be on the latest version of @vue/language-plugin-pug? That fixed the problem for me.

npm i -D @vue/language-plugin-pug@latest

[JayPuff]

Yep that worked, thank you so much 🎉