3.9.0

3.9.0 / 2021.09.15

• feat: support deno.json(c) files (#521)

  As of 1.14 Deno supports an expanded set of configuration options in the configuration file above the supported TypeScript "compilerOptions" options.

  The extension supports validating these configuration files, as well as recommends naming them deno.json or deno.jsonc.

• fix: debug config provider (#513)

• fix: better suppression of built in diagnostics (#514)

• chore: bundle extension (#506)

  This decreases download/install size of the extension as well as speeds up load time of the extension.

• chore: fix packaging of extension (#507)

• chore: update vscode typings (#519)

3.8.1

3.8.1 / 2021.08.25

• fix: properly parse config for test code lens (#502)
• chore: bump minimum version of Deno CLI (#503)

3.8.0

3.8.0 / 2021.08.10

• feat: add ability to set cache directory in settings (#477)

  The plugin supports setting the deno.cache option, which allows setting a
  specific cache directory for the Deno language server to use. This is similar
  to the DENO_DIR environment variable that can be set when invoking Deno on
  the command line.

• feat: hide the status bar unless deno.enable is true (#485)

  The Deno language server runs in a workspace even when the project isn't
  enabled for Deno, as the formatting services are still available and the
  language server needs to keep track of the state of documents in case the
  workspace does become enabled. It is confusing to see the version of Deno in
  the status bar. The extension now will not display this information unless the
  workspace is enabled for Deno.

• fix: properly handle plugin configuration at startup (#474)

  This led to an issue where if Deno started before the built in TypeScript
  language service in a Deno enabled project, the TypeScript language service
  diagnostics were not muted and incorrect or duplicate diagnostics were being
  displayed.

3.7.0

3.7.0 / 2021.07.02

• feat: add support for import map in test code lens (#446)

  When using the test code lens, the configuration of the import map is reflected in running the test.

• fix: activate extension on markdown / json / jsonc (#447)

• fix: setting then clearing "deno.path" config should not use empty string for path (#452)

• fix: better handling when language server fails to start (#454)

3.6.1

3.6.1 / 2021.06.08

• fix: update packaging and pin vsce version (#440)

3.6.0

3.6.0 / 2021.06.08

• feat: add support for tasks and test code lens (#436)

  The Deno Language Server as of Deno 1.11, code lenses for test are sent to the
  client, and the extension now supports allowing those tests to be run in the
  IDE. In addition, several tasks have been added to the extension which allow
  users to setup and configure common Deno CLI tasks via the tasks.json.
  Checkout out the testing and tasks
  documentation for more information.

3.5.1

3.5.1 / 2021.06.02

• fix: bump semver of extension (#429)

  This informs users that they require Deno 1.10.3 or later for the extension to properly work.

3.5.0

3.5.0 / 2021.06.01

• feat: recognize JSON(C) and markdown files (#404)

  This allows the Deno language server to be used as a formatter for JSON(C) and markdown files.

3.4.0

3.4.0 / 2021.05.11

• feat: handle per resource configuration (#411)

  Along with Deno v1.10, the extension now supports vscode's multi-root
  workspaces, which will allow you to enable and disable Deno per workspace
  folder.

• feat: add internalDebug config flag (#406)

  Enabling deno.internalDebug to true will output additional (quite verbose)
  logging information to help with diagnosing language server issues. This
  requires Deno v1.10 or later to work.

• fix: activate on reloadImportRegistries command (#407)

• docs: fix type in ImportCompletions.md (#410)

3.3.0

3.3.0 / 2021.04.13

• feat: add support for import registry completions (#380)
• feat: add restart language server command (#385)
• feat: add version notification message (#383)
• feat: support for relative path resolution (using workspaces) in deno.path (#381)