Eric
Eric2mo ago

VSCode only TypeScript Errors, nothing from Deno LSP

Hey, I've just restructured my pnpm workspace into a deno workspace. The Server and everything works already, but the vscode stuff isnt already. I've run >Deno: Initialize Workspace Configuration and I have a .vscode/settings.json, with this content:
{
"editor.defaultFormatter": "denoland.vscode-deno",
"editor.formatOnSaveMode": "file",
"deno.enable": true,
"typescript.tsserver.experimental.enableProjectDiagnostics": false
// "typescript.validate.enable": false
}
{
"editor.defaultFormatter": "denoland.vscode-deno",
"editor.formatOnSaveMode": "file",
"deno.enable": true,
"typescript.tsserver.experimental.enableProjectDiagnostics": false
// "typescript.validate.enable": false
}
If I uncomment the last line, I wont get the Typescript errors anymore-the problem is, i dont get any then. The Output of the LSP also seems reasonable, so I'm not too sure what to do here:
Starting Deno language server...
version: 2.1.10 (release, x86_64-unknown-linux-gnu)
executable: /home/eric/.deno/bin/deno
Connected to "Visual Studio Code" 1.96.4
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...
Server ready.
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...
Starting Deno language server...
version: 2.1.10 (release, x86_64-unknown-linux-gnu)
executable: /home/eric/.deno/bin/deno
Connected to "Visual Studio Code" 1.96.4
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...
Server ready.
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...
3 Replies
©TriMoon™
©TriMoon™2mo ago
"deno.enable": true should have been enough, i don't use any of the others...
CodyC
CodyC2mo ago
Same here. Did you manually add the typescript.* configurations? Deno's "initialize workspace" doesn't do that for me. That seems to be the problem?
Eric
EricOP5w ago
I’ve added that after initializing didn’t work

Did you find this page helpful?