Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

doc: Add new section to troubleshooting in VSCode Deno due to recent issue #402

Merged
merged 3 commits into from
Sep 30, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
feat: new section to troubleshooting vscode_deno
  • Loading branch information
khaosdoctor authored Sep 16, 2022
commit 9d5012c888211ce005a3c00958a98b6d694b9781
7 changes: 7 additions & 0 deletions vscode_deno.md
Original file line number Diff line number Diff line change
Expand Up @@ -382,6 +382,13 @@ This will display a document from the language server with a section named
_Workspace Configuration_. This will provide you with what vscode is reporting
the configuration is to the language server.

Also check if the VSCode configuration called `enableProjectDiagnostics`,
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 `"enable"` is set to `true` in there, and the error message still persists,
you might want to try restarting vscode, as the part of the extension that
"mutes" the built-in TypeScript diagnostics for files is not working as
Expand Down