Cannot find name 'svelteHTML' / Cannot find name '__sveltets_2_any', ....

[mysolo]

Describe the bug

bug on a version 109.2.2 , 109.2.1.
no bug on a version 109.2.0

use "svelte": "3.52.0" in a project.

VSCode return a multiple error on a

=> Cannot find name 'svelteHTML' on a each => Cannot find name '__sveltets_2_ensureArray' on a component => Cannot find name '__sveltets_2_any'

etc...

Reproduction

simple

Expected behaviour

No error on a code

System Info

• OS: Mac os X
• IDE: VSCode Version: 1.95.2
• Svelte for VS Code v109.2.2

Which package is the issue about?

Svelte for VS Code extension, svelte-language-server

Additional Information, eg. Screenshots

No response

[dummdidumm]

I am unable to reproduce this. Please provide a reproduction repository.

[mysolo]

[email protected]:mysolo/vsc-svelte-debug.git

I replace version for svelte/sveltekit/typescript.

clone repos
cd repos
vsc .

open page.svelte

[anders-hard]

I also got this after some VSCode upgrade(?) sometime over the last week.
OSX, Svelte 4.0.5, cursor 0.42.5, VSCode 1.93.1, Svelte for VSCode 109.2.2

[dummdidumm]

I am unable to reproduce this. Wondering if this is OS-dependent; I'm on Windows.

I suspect this came in as a result of #2561. Can you check

• whether or not there's a .svelte2tsx-language-server-files folder inside your node_modules?
• if yes what files does it contain?
• if yes what are the file contents? (they should not be empty)

[anders-hard]

Yes, I have three files. The svelte-html.d.ts is empty, the others are not.

[anders-hard]

I managed to get rid of the error by removing the node_modules folder, upgrading svelte and re-installing node modules. That removes the svelte-html.d.ts file (it would re-create if I deleted it before).

[dummdidumm]

I was able to reproduce this for the early Svelte 4 versions and fixed the bug related to that. Still not able to reproduce this for Svelte 3, but added some extra checks. @mysolo could you try with the latest version of the extension?

[mysolo]

@mysolo could you try with the latest version of the extension?

I still have the problem with version 109.2.3

[mysolo]

I am unable to reproduce this. Wondering if this is OS-dependent; I'm on Windows.

I suspect this came in as a result of #2561. Can you check

* whether or not there's a `.svelte2tsx-language-server-files` folder inside your `node_modules`?

yes

* if yes what files does it contain?

ls -al node_modules/.svelte2tsx-language-server-files git:(feat/posthog|…12⚑13
total 168
drwxr-xr-x 5 mysolo staff 160 Nov 9 01:39 .
drwxr-xr-x 82 mysolo staff 2624 Nov 9 01:39 ..
-rw-r--r-- 1 mysolo staff 64575 Nov 15 15:29 svelte-jsx.d.ts
-rw-r--r-- 1 mysolo staff 964 Nov 9 01:39 svelte-native-jsx.d.ts
-rw-r--r-- 1 mysolo staff 14526 Nov 15 15:29 svelte-shims.d.ts

* if yes what are the file contents? (they should _not_ be empty)

they not be empty

[dummdidumm]

This is truly strange. This means they are properly copied over into the hidden folder, but then not actually loaded or picked up, for whatever reason. I'm not sure how to investigate this further. @jasonlyu123 do you have any ideas how to help @mysolo debug this / any ideas why this could happen?

[dummdidumm]

@reskume mentioned this happens on case sensitive file systems, which may hint at what the problem is

[jasonlyu123]

So it might be something to do with inconsistent case sensitivity handling. Is the extension installed in the case-insensitive part of the system, while the project directory is in the case-sensitive part? But why is the write file work but read file doesn't? And why isn't that affecting normal files in the project?

@mysolo, can you confirm if you formatted part of your file system as case-sensitive? Though we are still not sure how this happened at least we can confirm if it's the same issue.

[mysolo]

@mysolo, can you confirm if you formatted part of your file system as case-sensitive? Though we are still not sure how this happened at least we can confirm if it's the same issue.

yes, all my dev projects are on a case-sensitive partition. Applications are on the standard os x partition.

[dummdidumm]

@mysolo / @reskume can you check if this still happens with the latest version of the extension?

[reskume]

I can confirm that in VSCode with extension Svelte v109.3.0 this has been resolved. Thanks a lot! Am Fr., 22. Nov. 2024 um 19:26 Uhr schrieb Simon H ***@***.***

…

: @mysolo <https://github.com/mysolo> / @reskume <https://github.com/reskume> can you check if this still happens with the latest version of the extension? — Reply to this email directly, view it on GitHub <#2584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABROSQHMRVKXG4DTQC77W3L2B5ZPFAVCNFSM6AAAAABRWWPUWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGQ4TEMRQGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mysolo]

it's ok for me :)

[Alex6357]

I still encountered this issue with extension v109.5.2, but it was resolved after restarting VSCode. Just a report.

These files are not empty.

[blaine]

I've also seen this issue intermittently. Restarting the Svelte language server seems to resolve the issue, but it seems to creep back. I've only noticed this in a svelte 5 project, not in my legacy svelte 4 projects.

[Oliver-Piorun]

Can confirm. The issue still exists 👍

Context:

• Svelte 5 project
• The files visible on @Alex6357 screenshot are also present in my node_modules folder
• Extension version: 109.5.2

[dummdidumm]

Please provide a reproduction repository along with steps how to reproduce

[Oliver-Piorun]

So today:

• Opened the project -> No error
• Deleted the node_modules folder and the pnpm-lock.yaml file
• Ran pnpm install
• Navigated to a *.svelte file
• Mentioned error is back again
  • The .svelte2tsx-language-service-files folder is missing

-> Restarting the Svelte LSP fixed this particular issue. It kicked in and created the mentioned folder.

^ Is this by design? If yes: I would love to not having to restart the LSP/VSCode when performing the listed steps.

I am not sure if this issue is related to the ones we observed in the past because the relevant folder was definitely present while the errors were displayed.

Thanks for your help 😊

[jasonlyu123]

I would recommend you always close the editor before deleting and reinstalling. There are all sorts of things that might get cached in different extensions. If you're reinstalling you obviously don't want some cache not being invalidated. It also doesn't make sense to trigger lots of file-watcher events in a short time reflecting changes that might be a total waste of time and might even slow down the reinstalling.