Facing an issue while migrating from [email protected] to [email protected]

[vijay-singh-16]

What happened?

I am using Vue and Quasar for a long-long time now. I have migrated my oldest Quasar project multiple times from v1 to the latest version.

Background:
For several years now I structure my vue components in a specific way. The component is split into two files e.g. HelloWorld.vue and HelloWorld.vue_.ts. The *.ts file contains only typescript code and the *.vue file mostly contains design elements (just like asp.net cshtml and cshtml.cs files in .Net).

This structure has many advantages due to which I keep using it till this day.

Earlier I migrated the project from webpack to vite (app-vite version '2.0.0-beta.12') and it was a success everything worked as it should.

Issue:
Now, since a stable version of app-vite is there, I migrated the project to the latest version. The project compiles and builds perfectly but vscode editor support doesn't work in *.vue files, like go-to-reference, view symbol details on hover, code completion intellisense, warnings and error squiggly etc.

I also created a new vanilla vue project with latest vite version and with the same component structure and it works perfectly well with full vscode editor support.

I tried many things to fix this issue but now ran out of ideas.

Kindly anyone, help me to resolve this issue as this may block my path to migration to newer quasar versions.

What did you expect to happen?

The vscode editor support should work as before.

Reproduction URL

https://github.com/vijay-singh-16/quasar-migration

How to reproduce?

Clone the reproduction repository

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)

Platforms/Browsers

Firefox, Chrome, Microsoft Edge

Quasar info output

No response

Relevant log output

No response

Additional context

No response