Should without npm like environment ignore the check for whether a single .vue file has vue dependency libraries?

[Linruoxin-Sy]

Vue (Official) version: 3.0.2

after I updated the new vue extension version. I got a error in a single .vue file in VsCode(version: 1.102.1) as follow

Write global types file failed. Please ensure that "node_modules" exists and "vue" is a direct dependency, or set "vueCompilerOptions.globalTypesPath" in "tsconfig.json" manually.vue(404)

After I checked the update information. I add jsconfig.json and vue-global-types.d.ts in my project then I successfully solved it.

However, adding jsconfig.json will cause the built-in Typescript check in VsCode. However, adding jsconfig.json will cause built-in Typescript checks or other checks in VsCode. This is not what I need. I think it might lead to unexpected error messages.

My vue project is in a fixed project template and does not require jsconfig.json and dependent libraries. It will eventually be handed over to a tool for compilation.

So, I think the check for whether the .vue file has dependent libraries should be applied to a project that already has a jsconfig.json or tsconfig.json file, or any other project that can be determined to be a possible vue project. Rather than directly acting on a single.vue file.

[KazariEX]

You are right. We should probably check if the current vue file exists in an inferred project instead of a configured project, and then skip the diagnostic of global types.