"Cannot find name" and other problems with TypeScript-SFC

[jankal]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: Win 10
• Vetur version: 0.22.1
• VS Code version: 1.37.0

Problem

Vetur underlines everything and gives errors like Cannot find name all the time.

Reproducible Case

At the moment I'm not sure how to make a reproducible case. The project is closed source and I'm not the author of most of the code. I mostly hope, that someone has seen this behaviour before.

[ktsn]

Are you enabling experimental template interpolation service? In that case what do you see when you execute Vetur: show corresponding virtual file and source map command?

[jankal]

@ktsn vetur.experimental.templateInterpolationService: true is not used in my config. I didn't even know this existed yet.

This is the output of Vetur: Show corresponding virtual file and sourcemap:

====================
Virtual content of c:\Users\alexa\Projekte\xqweb\roma-etk\assets\node_modules\@enhavo\svg-editor\Components\ApplicationComponent.vue.template
Hover, semantic diagnostics, jump to definition and find references are run on this file.
====================



====================
SourceMap
from: c:\Users\alexa\Projekte\xqweb\roma-etk\assets\node_modules\@enhavo\svg-editor\Components\ApplicationComponent.vue
to  : c:\Users\alexa\Projekte\xqweb\roma-etk\assets\node_modules\@enhavo\svg-editor\Components\ApplicationComponent.vue.template
[VueFileStart, VueFileEnd, VueFileText] => [TSVirtualFileStart, TSVirtualFileEnd, TSVirtualFileText]
====================

[ktsn]

That's strange because the errors looks only happens on template interpolation service. Could you try to produce it in available source code for us so that we can work on it? (e.g. extract culprit file, make the source code minimal to open etc.)

[ktsn]

@jankal I'm just looking #1451 which is possibly related to this issue. Is your problematic file in node_modules?

[msamsel]

@ktsn I hope this description will help you track down the error.

Same issue here. The way how I was able to make such error.
VSCode: version: 1.47.1
Vetur: 0.24.0
MacOS: 10.15.5

1. Open VSCode and create new file with button in on left file tree:
   
2. Name file with anything.Vue important part is to start extension with a capital letter.
3. VSCode will start to produce single error on the closing character of </template> tag:
   
4. Rename file (inside VSCode) to small later extension anything.vue
5. Fully close and open VSCode again
6. Open file with small letter extension.
   
7. Please notice that Vetur error still see file as test.Vue not test.vue as it is an actual name of the file. It looks like something somewhere is cached.

[jankal]

@ktsn Sorry for not having responded yet. The file wasn't in node_modules. I've not experienced this behaviour in other projects since then. Maybe @msamsel is on the right track here.

[Tehsurfer]

@msamsel's description is exactly what happened to me.

I tried deleting and recreating the file but still have the same error.

I've now switched to vscode-vue which seems to be working.

[KVINTH]

Just encountered this issue as well, same situation as @msamsel

Steps taken to address:

1. renamed File.Vue to File.vue (did not work)
2. created NewFile.vue and copied code from File.vue over
3. deleted File.vue
4. renamed NewFile.vue to File.vue

[legendarylion]

Yeah + 1 for @msamsel's description. Same for me. Renaming the file is fine - try to name it back, get smacked in the face with a wall of red (even though everything looks legit).

[msamsel]

@yoyo930021 do you think, provided description is sufficient to make a bug report from it?