Deno for Visual Studio Code
This extension adds support for using Deno with Visual
Studio Code, powered by the Deno language server.
⚠️ Important: You need to have a version of Deno CLI installed (v1.13.0 or
later). The extension requires the executable and by default will use the
environment path. You can explicitly set the path to the executable in Visual
Studio Code Settings for
Check here for instructions on how to
install the Deno CLI.
cards, intellisense, and more.
- Integrates with the version of the Deno CLI you have installed, ensuring there
is alignment between your editor and the Deno CLI.
- Resolution of modules in line with Deno CLI's module resolution strategy
allows caching of remote modules in Deno CLI's cache.
- Integration to Deno CLI's linting functionality, including inline diagnostics
and hover cards.
- Integration to Deno CLI's formatting functionality.
- Allow specifying of import maps and TypeScript configuration files that are
used with the Deno CLI.
- Auto completion for imports.
- Workspace folder configuration.
- Testing Code Lens.
- Provides Tasks for the Deno CLI.
- Install the Deno CLI.
- Install this extension.
deno is available in the environment path, or set its path via the
deno.path setting in VSCode.
- Open the VS Code command palette with
Ctrl+Shift+P, and run the Deno:
Initialize Workspace Configuration command.
in VSCode uses Deno — therefore, by default, this extension will only apply the
Deno language server when the setting
deno.enable is set to
true. This can
be done via editing the settings or using the command Deno: Initialize
While you can enable Deno globally, you probably only want to do that if every
The extension provides several commands:
Deno: Cache - instructs Deno to fetch and cache all the dependencies of the
current file open in the editor. This is similar to doing
deno cache on the
command line. Deno will not automatically fetch and cache remote dependencies.
ℹ️ If there are missing dependencies in a module, the extension will
provide a quick fix to fetch and cache those dependencies, which invokes
this command for you.
Deno: Initialize Workspace Configuration - will enabled Deno on the current
workspace and allow you to choose to enable linting and Deno unstable API
Deno: Language Server Status - displays a page of information about the
status of the Deno Language Server. Useful when submitting a bug about the
extension or the language server. _ Deno: Reload Import Registries Cache -
reload any cached responses from the configured import registries.
Deno: Welcome - displays the information document that appears when the
extension is first installed.
and TSX documents. When choosing to format a document or setting up a default
formatter for these type of files, the extension should be listed as an option.
ℹ️ It does not currently provide format-on-paste or format-on-type
You can control the settings for this extension through your VS Code settings
page. You can open the settings page using the
Ctrl+, keyboard shortcut. The
extension has the following configuration options:
deno.enable: Controls if the Deno Language Server is enabled. When enabled,
language services, and will use the Deno Language Server (
deno lsp) instead.
deno.path: A path to the
deno executable. If unset, the extension will use
the environment path to resolve the
deno executable. If set, the extension
will use the supplied path. The path should include the executable name (e.g.
deno.codeLens.implementations: Enables or disables the display of code lens
information for implementations for items in the code. boolean, default
deno.codeLens.references: Enables or disables the display of code lens
information for references of items in the code. boolean, default
deno.codeLens.referencesAllFunctions: Enables or disables the display of
code lens information for all functions in the code. Requires
deno.codeLens.references to be enabled as well. boolean, default
deno.codeLens.test: Enables or disables the display of test code lens on
Deno tests. boolean, default
false. This feature is deprecated, see
deno.codeLens.testArgs: Provides additional arguments that should be set
when invoking the Deno CLI test from a code lens. array of strings, default
[ "--allow-all" ].
deno.config: The file path to a configuration file. This is the equivalent
--config on the command line. The path can be either be relative to
the workspace, or an absolute path. It is recommended you name this file
deno.jsonc. string, default
deno.importMap: The file path to an import map. This is the equivalent to
--import-map on the command line.
provide a way to "relocate" modules based on their specifiers. The path can
either be relative to the workspace, or an absolute path. string, default
deno.internalDebug: If enabled the Deno Language Server will log additional
internal diagnostic information.
deno.lint: Controls if linting information will be provided by the Deno
Language Server. boolean, default
deno.suggest.imports.hosts: A map of domain hosts (origins) that are used
for suggesting import auto completions. (See:
ImportCompletions for more information.)
deno.testing.args: Arguments to use when running tests via the Test
Explorer. Defaults to
[ \"--allow-all\" ].
deno.testing.enable: Enable the testing API for the language server. When
folder is Deno enabled, tests will be available in the Test Explorer view.
deno.unstable: Controls if code will be type checked with Deno's unstable
APIs. This is the equivalent to using
--unstable on the command line.
We appreciate your help!
To build the extension locally, clone this repository and run the following
- Open this folder in VS Code.
- Run the
Launch Client launch task from the VSCode debug menu.
After making changes to the extension you can use the restart button in the
VSCode debug menu, this makes a new build and reloads the client.
Note that if you already have the deno extension installed from the VSCode
Marketplace, it will be replaced for the
Launch Client instance only. So
there's no need to uninstall your existing Deno extension.
Most changes and feature enhancements do not require changes to the extension
though, as most information comes from the Deno Language Server itself, which is
integrated into the Deno CLI. Please check out the
contribution guidelines for the Deno
This project was inspired by
axetroy/vscode-deno. Thanks for their
The MIT License