Roadmap

With numerous reports about extension being broken (#110, #99, #120) I’m opening this issue to clearly communicate our plans regarding the extension and what can be expected of it.

First of all, this project is not dead, even though there hasn’t been much development going on. Deno team is aware of the problems plaguing the VSCode extension and we’re allocating time to work on the extension and the LSP implementation.

We plan to work on the better implementation of language server first, because it is used by other IDEs besides VSCode (eg. CoC, IntelliJ).

In the long run, we’d like to provide this server directly built-in into Deno binary.

However for the first iteration might end up being an update to typescript-deno-plugin package to get put out most of burning fires (#99, #85, #49) and provide stable and tested solution.

After sorting out problems with the language server we’ll change our focus to the VSCode extension itself. Again, first we’ll tackle currently occuring bugs to ensure the “basic” workflow is satisfactory and working properly.

We’ve got limited bandwith so I’m not willing to give any date estimates at the momoent, as to when to expect fixed version of the language server and extension.

If you’re experienced in developing either of these things and would like to contribute don’t hesitate to comment on this issue.

[jsejcksn]

@David-Else The changelog you linked to does not represent the actual changelog of this extension. It seems to have been copied from axetroy’s extension during the switch I mentioned above.

[David-Else]

@bartlomieju I think this post might have been outdated by the recent merge, also there is a mismatch between version numbers now https://marketplace.visualstudio.com/items/denoland.vscode-deno/changelog vs https://github.com/denoland/vscode_deno/commit/9d121207d8c1b9b9ad86a5b441d1bc674ca3fc14