vscode_deno: Extension is not working

Describe the bug hey i’ve installed latest deno version 1.3.0 , and have vscode insiders installed , before one week everything was working fine , yesterday i opened vscode , but the suggestions are not working i have vscode insiders version 1.48.0 , and whenever i try to import some urls it gives red line errors

Expected behavior

extension should give suggestions,

Versions

vscode: 1.48.0 deno: 1.3.0 extension: 2.0.4

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 20 (4 by maintainers)

Most upvoted comments

The extension was working for me fine yesterday with just "deno.enable": true. Today it’s not working at all. There is no difference if it’s installed or not. The only thing that changed was windows update but I doubt that has anything to do with it.

Btw, installing dependencies using npm is not a solution because Deno projects should not require anything Node related to work.

Voycawojka on Aug 15, 2020

Sorry for the breakage. 2.0.11 should be released momentarily with the fix.

ry on Aug 15, 2020

Currently on 2.0.13. This does not appear to have been fixed, or at least not in the way that I had hoped 😅 I am currently missing autocomplete for any type of external dependency that imports/re-exports from local dependencies (any dependency from std for example).

// deps.ts
export * as path from "https://deno.land/std@0.64.0/path/mod.ts";

// mod.ts
import { path } from "./deps.ts";
path.resolve("xyz");

gives the following result:

jeroenptrs on Aug 15, 2020

The extension seem to break since https://github.com/denoland/vscode_deno/commit/ce7de3dc9713260f0db734816a93b74c08669e14

axetroy on Aug 15, 2020

@ry @bartlomieju So I am having the same issue, and it seems to be related to typescript-deno-plugin not being loaded because it can not be found. I got this https://gist.github.com/lucacasonato/161064ddc428661faf6abb767b18a44a from my tsserver.log. It seems that somehow the typescript-deno-plugin isn’t being built, (or included in the vsix package). This would also explain the weird behaviour a few versions back where the vscode plugin was the 2.x, but the typescript-deno-plugin seemed to still be running at the 1.x version.

@2nini @lem0nify @newtack @WhoAdarshPandya Could you all upload the contents of your tsserver.log (access by pressing Ctrl-Shift-P in VSCode, then > Typescript: Open TS Server log) to Gist and paste the link here?

lucacasonato on Aug 15, 2020

I have exactly the same problem. It worked with code-insiders yesterday, it doesn’t work today with the the latest code-insiders nor with the just release vscode 1.48.

I have set deno.enable=true in .vscode/settings.json.

The only Deno command left is “deno: Restart Deno Language Server”.

I am using Ubuntu 20.04, latest updates.

Edit: Noticed that both VSCode and the extension and the Typescript plugin changed. So not sure which it was. It did still work yesterday with Deno 1.3.0 so that should not be the problem.

newtack on Aug 15, 2020

Make sure that you have enabled the extension in .vscode/settings.json with deno.enable = true

Skillz4Killz on Aug 14, 2020