Autocompletion doesn't work anymore in typescript files

[Olyno]

Describe the bug

Following the discussion on Discord, it looks like the new versions of the extension break autocomplete: 107.2.1 and 107.2.2

Reproduction

Create a new Svelte kit project, add a server route, and tada, try to use autocomplete.

Expected behaviour

It should autocomplete fetch in the below example.

System Info

• OS: Linux
• IDE: Vscode

Which package is the issue about?

Svelte for VS Code extension

Additional Information, eg. Screenshots

[thelinuxlich]

Can confirm this bug

[alumpe]

Can confirm the bug for WSL2 on Windows 10. Normal .ts files have no issue, it is just + prefixed sk files.

[dummdidumm]

This is hopefully fixed with version 107.2.3.

[vnphanquang]

Sorry, is it me or did we all lose the type inference for *LoadEvent (as shown in https://svelte.dev/blog/zero-config-type-safety)?

Env Info

• OS: linux (ubuntu 22)
• VSCode v1.76.1
• Svelte Extension v107.2.3

Tested in project bootstrap with create-svelte@latest, all latest dependencies:

{
	"@sveltejs/adapter-auto": "^2.0.0",
	"@sveltejs/kit": "^1.11.0",
	"eslint": "^8.36.0",
	"svelte": "^3.56.0",
	"svelte-check": "^3.1.2",
	"tslib": "^2.5.0",
	"typescript": "^4.9.5",
	"vite": "^4.1.4",
}

Dev server was running; VsCode was reloaded, no luck still in all +*.ts files. It's worth noting, however, that typing for data prop in +*.svelte files is correctly inferred.

Maybe related: sveltejs/kit#9400

[ghostdevv]

@vnphanquang You need to give that function a type

import type { PageServerLoad } from './$types';
 
export const load = (async (event) => {
}) satisfies PageServerLoad;

[vnphanquang]

@ghostdevv yeah, that has been the way, but not anymore (supposedly) in latest tooling support as shown in https://svelte.dev/blog/zero-config-type-safety though

[ghostdevv]

Ah, missed that - awesome! I'm not sure why it wouldn't work in that case 🙏

[jasonlyu123]

Did you enable the svelte.enable-ts-plugin config?

[vnphanquang]

@jasonlyu123 yeah it's been on for me the whole time.

{
    "svelte.enable-ts-plugin": true
}

All other config options under svelte.* are left to default.

Not that it's helpful, but it did work for me for a split second after I opened vscode, but then not any more after that for any load function (while it's still okay for data in +page).

[jasonlyu123]

The plugin may be enabled for a small window before the API we use turns it off. You can check if it is on in your user config but off in your workspace config. If it isn't the case, please open another issue with reproduction. It is likely a separate issue.

[vnphanquang]

Understood, thanks for the instruction. No workspace config in my case indeed. I'm gonna give it some time before opening another issue, maybe it's something from my setup i've not taken into account.