Deno•2y ago

VSCode starting Deno even if enabled=falseI

I use VSCode in a large project (with several JS packages, none of which use Deno), and after installing the Deno extension, the typescript extension fails to start (crashes 5 times and then gives up).

My understanding is that by default, Deno isn't supposed to start, for this very reason, but it still is? I do not have a deno.json file anwyhere, and I've even tried setting

deno.enable

deno.enable

false

false

.vscode/settings.json

.vscode/settings.json

. Any idea what might be going on?

Ankur GoyalOP•1/24/24, 10:17 PM

And to clarify, if I disable Deno's extension in the workspace, things work just fine

Deno AI Helper•1/24/24, 11:12 PM

Based on the documentation, the Deno extension for VSCode should indeed be disabled by default. If you've explicitly set

deno.enable

deno.enable

false

false

in your

.vscode/settings.json

.vscode/settings.json

file, the Deno Language Server should not be enabled.

However, there are a few things you could check:

Make sure that the
```
deno.enable
```
```
deno.enable
```
setting is correctly set in the right settings file. VSCode has both user settings and workspace settings. The
```
deno.enable
```
```
deno.enable
```
setting should be in the workspace settings (
```
.vscode/settings.json
```
```
.vscode/settings.json
```
) for your project.
Check if the VSCode configuration called , located in TypeScript › Tsserver › Experimental: Enable Project Diagnostics is disabled. This setting allows TypeScript language server to execute in the background to check the entire project at once and Deno cannot disable its behaviour so the errors keep showing even when all other settings are correctly set.
If the issue persists, try restarting VSCode. Sometimes, changes in the settings require a restart to take effect.
If none of the above solutions work, it's possible that you've encountered a bug. In this case, you should report the issue on the Deno extension's GitHub repository at https://github.com/denoland/vscode_deno.

Remember, the Deno extension for VSCode is designed to work in a way that it doesn't interfere with non-Deno projects. If it's causing issues, it's likely due to a misconfiguration or a bug.

Helpful Links:
Using Visual Studio Code | Manual | Deno
Deno 1.6 Release Notes
Configuration | Manual | Deno
Deno 1.21 Release Notes

bartlomieju•1/24/24, 11:36 PM

CC @nayeemrmn

Ankur GoyalOP•1/24/24, 11:52 PM

i've tried all of the above and unfortunately did not work