Roadmap 2

Now that most burning fires have been put out #121 can be closed and it is time for a new roadmap. The goals for the next few weeks and months should be stabilizing the extension, improving compatibility with mixed Node + Deno projects, and making the extension more easy to use. Here are some ideas in rough order of priority (top is most important):

• editor.defaultFormatter should not be hijacked by deno fmt
• ~Implement "deno.include" setting to enable the extension on files matching this path.~ not possible until deno lsp
• ~Implement "deno.exclude" setting to disable the extension on files matching this path.~ not possible until deno lsp
• Various improvements to language server. (#187)
• Add Deno debugging configuration.
• Re-add Enable Deno and Disable Deno commands to quickly switch "deno.enable" in .vscode/settings.json. (#170)
  • This was instead covered by Init command.
• Support re-exports from files like deps.ts for autocomplete.
• Support configuration in workspace and user settings, not just project settings.

And various high priority bugs that need to be fixed:

• Syntax highlighting is somewhat broken (#150)
• @deno-types does not work on first load (#97)

---

The future goal is still to integrate LSP into the deno binary.

[CGQAQ]

@lucacasonato First one should be checked due to #193 closed, in fact, fmt is not been hijacked at all. See this: microsoft/vscode#106376

[lucacasonato]

We now use deno lsp in version 3.x of the extension. The roadmap issue for lsp is https://github.com/denoland/deno/issues/8643. Closing this issue.